What's new in Oracle Policy Automation August 2016?

Enhanced interview statistics

Interview statistics in Oracle Policy Automation (OPA) Hub have been enhanced to see trends at a glance of the usage rates of each deployed interview. This enables interview authors to quickly detect changes in success rates as customer demographics or scenarios change.

Preset charts are now provided for useful information such as interview duration and screens visited. This information can be used to optimize interviews to reduce abandonments and accelerate time to successful completion.

Tailor multi-channel interviews to different audiences

Multi-channel interviews can now be customized for the different Oracle Service Cloud user types (Agent, Contact and Anonymous). This works with any Service Cloud connection and enables you to, for example, provide agents with links to internal policy and detailed reasons for decisions, without compromising the customer experience. For more information, see:

Enhanced relationship handling

Entity functions have been enhanced to enable Policy Automation to be integrated with a wider variety of applications, without customized connector development. These changes allow you to now:

Separate input and output entities in order to create data models that match the connected application’s schema

Make decisions and calculations based on data shared across relationships

Model policy or calculations that rely on inductive logic

New rule syntax (the InferInstanceFor function) is used to create related entity instances.

Existing rule syntax (the InferInstance function) is now able to infer that the relationship is complete in more cases, allowing you to create chains of inferred entity instances. All other entity functions remain unchanged.

The entity documentation has also been improved to include worked examples, complete with downloadable policy model to run the example locally.

RuleScript

RuleScript uses industry-standard JavaScript to extend what is possible with OPA rules. These scripts are typically implemented by partners or IT specialists and incorporated into an existing or new OPA project as a separate type of asset. Each RuleScript rule works with the attributes, entities and relationships of the OPA data model to make decisions and perform specialized calculations.

Temporal values supported in test cases

Temporal values are now supported as input and expected outcome values. Test case execution will populate temporal values when they occur as outputs. For more information on the formatting expected for temporal values in test cases, see:

Notification in Debugger when project has changed

The Debugger now notifies the user if the project has changed since the debug session started. Users can click the Apply button in the notification to apply the changes and retain the session data. For more information, see:

Other enhancements

For projects with large Excel rule tables (for example, with lots of reference data), debugging and deploying are now much faster. Starting interviews is also now much faster.

For projects with Service cloud connections, interviews are no longer limited to submitting 100 Service Cloud objects.