What are the key concepts in Policy Automation?
Oracle Policy Automation (18A release)
The following are the key concepts in Oracle Policy Automation:
|Policy Modeling||Policy Modeling is a desktop application used to develop policy models and interactive interviews based on business requirements, policy and legislation.|
|Hub||Policy Automation Hub is a browser-based management console which provides policy modeling project and user administration functions.|
|Projects||Policy Modeling projects manage the rule documents, the data model and the interview definition that make up a policy model.|
|Attributes||An attribute is a unit of data or fact. Attributes can either have a true/false value or take on a variable value (for example, a number, date, text and so on).|
|Entities||An entity represents a group of things (for example, people, objects, concepts) with rules or data in common.|
|Relationships||A relationship defines how two entities relate to each other so that rules can be written that reason from one entity to another.|
The data model in Policy Modeling consists of the entities, relationships and attributes that make up the policy model.
The connection of Oracle Policy Automation (OPA) entities and attributes to tables and fields in a data source.
|Rules||Rules specify the logical relations between attributes and provide a framework against which attributes can be tested to determine their value. Rules describe relationships in terms of if-then logic.|
|Temporal reasoning||Temporal reasoning is the ability to reason with policy model attributes or outcomes for which the values change over time. Rules written in Policy Modeling are thus time-aware, operating simultaneously both at a specific point in time, as well as across time periods.|
Translation documents are Excel files in which translations are maintained of all the text that can appear when projects are deployed. This allows you to deploy a single policy model in multiple languages, while continuing to develop the policy model in its original language.
|Debugging||Debugging is the process of testing the logic of your rules to confirm that inputs match expected decisions.|
|Interviews||An interview is a web-based application which collects information from a user to find values for policy model goals.|
|Forms||A form is a document that can be generated from an interview to provide the user with a record of the interview, including answers and conclusions. Forms have many uses, including pre-filled claim forms and advice letters.|
|Explanations||An explanation is a tailored list of reasons about how the value of the goal attribute was determined. It can be added to an interview or form to give the reasons for a particular decision. It is most suitable for displaying to customers and agents.|
|Audit reports||An audit report is a complete list of reasons about how the value of the goal attribute was determined. It is available in connected interviews without requiring any report configuration. It is most suitable for displaying to auditors.|
|Rule testing||Policy testing is the act of reviewing the outcome of rules, usually to ensure the rules are returning the correct results.|
|Users||OPA users are needed for interacting with Policy Automation Hub, for the purposes of managing project versions and deployment, and for administering other users.|
|Deployment||Deployment is the first step in the process of making a project snapshot available for Oracle Policy Automation interview and web service interactions, and for use on mobile devices (the other step is activation). Deploying a project is performed in Policy Modeling. Deployment is managed via Policy Automation Hub.|
|Activation||Activation is the second step in the process of making a project snapshot 'go live' for end users (the other step is deployment). Activation can be performed within Policy Modeling at the time of deployment, or later from Policy Automation Hub. End users can then interact with the policy model via the deployment option specified for it (as an OPA interview or as a web service or both).|
|Connections||Connections are used to retrieve metadata from external data sources such as Oracle Service Cloud or web service data sources, and are how data is saved and loaded by interviews at runtime.|
|Collaboration||An optional set of features is available for collaborative policy modeling and versioning, allowing fine-grained version control for Policy Modeling project development, and supporting multi-developer projects. Managed from Policy Automation Hub Repository tab. To enable these features contact your Oracle sales representative.|
A value list, otherwise known as an enumeration, is a tool for managing lists of potential values for a non-boolean attribute in your policy model.
|Inclusions||An inclusion is a policy modeling project that has been imported into another policy modeling project for the purpose of reusing some or all of the project’s assets.|
|Reference Tags||The structural elements in legislation (section, paragraph, sub-paragraph and so on) or policy (guidance, chapter, criterion and so forth) can be annotated in rules using reference tags. By tagging conclusions and conditions with the applicable part of the source material, rule authors are able to easily keep track of, and show, the sources used in every decision.|
Would you like help collecting this information?Yes, let's chat!