Skip Navigation
Expand
What is new in Oracle Oracle Policy Automation 19D
Answer ID 11294   |   Last Review Date 12/20/2019

What is new in Oracle Policy Automation 19D?

Environment:

Oracle Policy Automation (OPA), new features

Resolution:

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

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

Entity level forms

This release provides the ability to generate a form for entity instances. (Previously, a form's data was always based on the global entity.) For example, an advice getter could now download or submit a separate application form for each member of a household (where the household is the global entity and the household member is an entity).

For more information, see:

Allow submitted interview data to be updated

Interview authors now have the option to allow users to edit previously submitted data and re-submit their interviews via the same submit button. This enables interview users to update a particular case as often as required. This feature is only supported for Latest version web service connected interviews (including Engagement Cloud).

For more information, see:

Refresh seed data

Interview authors now have the option to allow mapped in seed data to be refreshed at specified points during the interview. When a seed data refresh occurs it triggers the same seed data process as happens at the beginning of the interview. That is, it issues a request to the connector to get the data specified by the input mapping and then loads that data into the session. This feature is only supported for Latest version web service connected interviews (including Engagement Cloud).

For more information, see:

Other enhancements

New Policy Automation Hub user interface

The Policy Automation Hub user interface has been updated to make it more consistent with the Oracle JET look and feel. The new UI is more technically aligned with devices, having a responsive layout and accessibility, and enables OPA to better deliver the functionality that our customers require.

For more information, see:

Pass a cookie parameter in the OAUTH header for embedded interviews

For a web service connection, there is now the ability to name a cookie which will be passed through in the parameters of any Load, Save, GetCheckpoint or SaveCheckpoint request made the query. This enables customers that authenticate users of their interviews via an OAUTH token passed in a cookie to have that same token passed when the data adaptor is invoked during an interview.

For more information, see:

To keep up-to-date on OPA, see How can I stay informed about Oracle Policy Automation?

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

Available Languages for this Answer:

Notify Me
The page will refresh upon submission. Any pending input will be lost.