Example: Data Mapping Settings for Interviews with Customer Portal Users

Example 1. Setting up an interview that only pre-seeds the interview with Contact data.

For instance, this may be used to provide a bank’s existing customers financial advice based on their personal circumstances.

Mapping Settings dialog in Oracle Policy Modeling showing Contact option selected

Example 2. Setting up an interview that pre-seeds the interview with Contact data and will allow Contacts to update their data and create multiple child records.

For instance, this may be used for self-service updating of personal details, such as change of address.

Mapping Settings dialog in Oracle Policy Modeling showing Contact option selected with Update Contact option selected

To create child records, for example multiple tasks at the end of the interview, see Save Data to Application Tables From Other Entities.

Example 3. Setting up an interview that pre-seeds the interview with Contact data and creates a new Incident record at the end of the interview.

For instance, this may be used for self-service logging of claims or warranty issues by existing customers.

Mapping Settings dialog in Oracle Policy Modeling showing Contact option selected with Create new Incident option selected

Note that if you want to create a single new Incident record that is not related to the Contact at the end of the interview, you should deselect the Relate to Contact via check box.

Example 4. Setting up an interview that pre-seeds the interview with Contact and Incident data, and updates the Incident at the end of the interview.

For instance, this may be used for self-service updates to existing customer support issues.

Mapping Settings dialog in Oracle Policy Modeling showing Contact option selected with Incident and PrimaryContactIncidents options and Update Incident option selected