Name Tables, Fields and Links

Objects (tables, fields and links) in the GetMetadata response need to have name attributes. In choosing names for these objects, be aware of the following:

  • These names will appear in Policy Modeling. It is therefore preferable that the names you choose include enough semantic content to assist non-technical policy modelers with data mapping (for example, 'Person’s Age').
  • These names will also be used by the Load and Save actions.
  • You are responsible for implementing any translation between the table, field and link names which requests and responses contain into the equivalent names of the objects in the underlying application.
  • You can set names to match the names in the underlying database so that requests do not need to be translated from the abstraction layer to the database layer, however database-identical names (for example 'col_24') may be confusing or meaningless to a policy modeler.
  • Spaces can be used in names, further increasing the aesthetic appeal of the naming compared to using the database’s column name.

For example:

<get-metadata-response xmlns="http://xmlns.oracle.com/policyautomation/hub/12.2.13/metadata/types">
    <Table name="Products" can-be-input="true" can-be-output="false">
        <Link name="Cameras" target="Camera" cardinality="C_1M"/>
    </Table>
    <Table name="Car Request" can-be-input="false" can-be-output="true">
        <Field name="request_ID" type="DECIMAL" can-be-input="true" can-be-output="false" is-required="true"/>
        ...
    </Table>
</get-metadata-response>

Related Topics