What is new in Oracle Policy Automation 17D
Answer ID 9884   |   Last Review Date 11/15/2017

What is new in Oracle Policy Automation 17D?


Oracle Policy Automation (OPA), new features


Do you have a deployed project created in an earlier version? There are a few things you should check.

The 17D release of Oracle Policy Automation Cloud Service includes: 


Dynamic reference data loading

Oracle Policy Automation (OPA) now supports the loading of any additional data from Service Cloud or the connected application, even if it is unrelated to the contact, opportunity and so on for the interview. You can define conditions for which reference data items to load, using filters and rules. Data is retrieved automatically during an interview session, as soon as the specified conditions are met.

This feature ensures great performance for interviews that need to load data dynamically from a large set of reference data, such as orders or products. A single source of truth can be maintained for product catalogs, so that up-to-date guidance to the most suitable products is always provided.

For more information, see:


Sales and Engagement Cloud interview styling

A Sales and Engagement Cloud interview theme option is now provided so that OPA interviews that are embedded in Sales and Engagement Cloud can have a consistent look and feel. The styling matches the default Sales and Engagement Cloud styling and can be easily updated as needed to match the actual Sales and Engagement Cloud theme configuration. The default styling changes the appearance of buttons, puts buttons inline with the navigation bar, moves question text beside the control, and more. Using these features to adopt compact layouts enables interviews to work responsively on both mobile and desktop screens.

For more information, see:


Identity Cloud Service integration

The OPA Hub user life-cycle can now be centrally administered through a linked Identity Cloud Service tenancy. This provides Single Sign-On for OPA Hub users, including authoring, administration, mobile and API user roles. (Fine-grained permissions are still managed within the OPA Hub administration experience.)

This feature has the benefit of easily synchronizing employee access to the OPA Hub with their on-boarding and off-boarding life-cycle. It also simplifies the management of OPA user access, particularly for large user populations such as mobile field agents, and with other Oracle cloud applications.

For more information, see:


Interview modeling enhancements

Configure submitted form name and location

OPA has simplified the finding and identifying of generated forms in connected applications. Interview designers can now configure the generated form name and have attachments saved to any entity. For example, if multiple opportunities are created, a summary document could be generated and added to each one. For more information, see:


Easily debug generated forms

Interview designers can now easily ensure the correct appearance and behavior of uploaded documents. The Debugger shows which forms will be attached on submit, and enables uploaded forms to be previewed directly. For more information, see:


Round-trip test case debugging

Testers can now navigate from a test case to the Oracle Policy Modeling Debugger and back again. When launching the Debugger from a test case you can see which test case is being debugged, and while debugging you can navigate back to where a test case value is defined. For more information, see:


Provide names for screen layout containers

To simplify the maintenance of nested interview layouts, meaningful container names can now be added to explain their purpose and how they contribute to the screen layout. For more information, see:


Collect global/parent data on entity screens

Interview designers can now add Global (parent) entity content to entity-level screens. This could be used to collect data for global and parent entities on multiple screens, for example, so that the user could update certain data (like product choices or notes) on every screen of an interview. For more information, see:


Interview experience enhancements

Change language during an interview

The user interface language of an interview can now be changed at any time. This is done through the inclusion of a change language button in the header or footer (or both) of the interview. This can simplify the integration of multi-language interviews into customer portals. This feature also works with interview extensions. For more information, see:


Execute project test cases from the command line

A command-line utility is now available for running test cases (OPMRunTests.exe). This allows testers of integrated solutions to include policy model test case results and execution timing in their automated testing. The command-line tool can generate reports of the test case results in various formats (XML, HTML, JUnit) and testers can have these checked by staff that may not even have Policy Modeling. For more information, see:


Show icons for optional questions

When optional questions are less frequent than mandatory ones, a visual indicator of only the optional questions can be used to simplify the interview experience. For more information, see:


Interview integration enhancements

Set attribute values in resumesession URL

You can now specify that reviews or other special behavior should be triggered when an interview is resumed. For example, if an interview is being resumed more than 14 days after it was started, you could require the interview user to reconfirm their previously provided answers. For more information, see:


Seed entity level data via startsession URL

Using the startsession URL you can now pre-populate entity collections or provide some dynamic reference data when an interview is launched. For more information, see:


Hub enhancements

Set default channels for any collection

Hub Administrators can now specify the default channels for any collection. This eliminates the need to manually reconfigure every new deployment to use the correct channels. There is also the option to lock the channels for existing deployments. For more information, see:


Rule modeling enhancements

If and Default rule functions

Several new rule functions have been added that can be used to simplify rules.

The new If() function enables rules that use nested conditions to be simplified by instead testing conditions without creating separate rules. This means that intermediate attributes only have to be created when they are needed.

The new default functions enable policy models to be simplified where default values are required. The Default() function can be used to set an attribute value if none was provided (that is, where the value is uncertain). This can be useful in interviews where unfilled answers need to provide a default result. The DefaultWithUnknown() function can be used to set an attribute value if the value is uncertain or unknown, thereby always returning a known result.

For more information, see:

Faster migration of Word documents from 10.4

OPA 10.4 projects containing large rule documents can now be migrated to OPA version 12 quickly, enabling the migration to be repeated if necessary. For more information on migration, see:



For a list of issues addressed in this release, see the Policy Automation Change History (Active customers only).

Would you like help collecting this information?

Yes, let's chat!

Viewing our site using a mobile device? Our mobile pages are just a tap away.

View site in: Desktop | Mobile