How are data mappings established in Oracle Policy Automation interviews?
Oracle Policy Automation, latest release
Data mapping enables you to pre-seed data in an Oracle Policy Automation interview from Oracle Service Cloud and to save outcomes from the interview to Service Cloud. To do this, data in Oracle Policy Automation needs to be mapped to corresponding Service Cloud objects and fields.
Order of data mapping
Data mapping is done at three levels, and in this order:
- Mapping the Global entity in Oracle Policy Automation to the equivalent objects in Service Cloud. The global entity instance in Oracle Policy Automation can be bound to a maximum of three objects in Service Cloud:
- the user context
- an additional top-level input
- a top-level output
- Mapping the non-global entities in Oracle Policy Automation to the equivalent objects in Service Cloud. This also binds the relationship (or the link between the objects) in Service Cloud to the Oracle Policy Automation containment relationship. Note that the mapping of reference relationships is not currently supported for Service Cloud connections.
- Input mapping and output mapping individual attributes in Oracle Policy Automation to fields in the objects of Service Cloud.