Understand How to Expose Application Metadata

The exposure of the metadata of your application to Policy Modeling is implemented as an abstraction layer on top of your application. Non-technical policy modelers will need to easily understand and identify the names of objects in this abstraction layer, so bear this in mind as you decide what to include and what to call it.

Policy Modeling uses a containment data model for projects. The general principle is that tables in the application correspond to entities in Policy Modeling, and fields in the application correspond to attributes in Policy Modeling. For more information, see Data Map to Oracle Fusion, B2C Service, Siebel, Or Another Specific Application.

However, you have a great deal of flexibility in how you structure your abstraction layer and in what you include. The abstract layer is generally a rough representation of an underlying application for the sake of simplicity, but you may choose to do any of the following to assist in the mapping process for policy modelers:

• hide some tables and fields,
• describe additional tables and fields in the layer which are not representative of the application,
• 'flatten’ the fields of a table into another table to reduce the number of tables exposed to Policy Modeling.

Foreign key constraints are represented as 'links' but these are similarly exposed as an abstracted type to conform to the containment relationship model used by Policy Modeling.