Defining the object model for a namespace

The Object Model setting is required. It contains the relationship path that is used for reporting in a namespace. A namespace cannot contain ambiguous paths.

The framework generator uses the value pairs in this setting to define the parent-child relationships in the generated framework model.

Platform > Reporting Framework V6 > Models > [model name] > Namespaces > [namespace name] > Object Model
Default:
Values: In the Value field, enter value pairs to reflect parent-child object relationships. All parent-child paths must start with SOXBusEntity. The syntax is: 
<parent object>|<child object>,<parent object>|<child object>

For example: 

SOXBusEntity|SOXProcess,SOXProcess|SOXRisk,SOXRisk|SOXControl

System-supplied namespaces

If you change the Object Model setting in the pre-defined namespaces in the pre-defined framework model folders, the change can affect the functionality of the pre-defined reports that are supplied with OpenPages®.

Supported triangle relationships

If you want reporting capability for object types that are in a triangle relationship and have configured the Supported Triangle Relationships setting, the paths between these object types must be reflected in the Object Model setting of a namespace. The namespace can be either new or existing. For details on configuring the Supported Triangle Relationships setting, see Triangle object relationships.

Configuring secondary compliance objects for basic framework models

If the namespace is used in a basic framework model, you must define allowed relationships between primary and secondary compliance objects in the Object Model setting.

  • Secondary compliance object relationships must be added to the Object Model setting for the namespace, for example, SOXBusEntity|SOXIssue.
  • You can define multiple relationships for a secondary compliance object, for example, SOXBusEntity|SOXIssue,SOXProcess|SOXIssue.
  • Relationships between secondary compliance objects must be explicitly defined, for example, SOXIssue|SOXTask.

When the reporting framework is generated:

  • Secondary compliance objects are generated like other objects but will have a hyphenated name that includes their parent object, for example, Business Entity - Issue.
  • A query subject is created for each relationship defined, for example, Business Entity - Issue, Process - Issue.
  • Relationships between two secondary compliance objects are generated within the context of a primary compliance object. For example, SOXBusEntity|SOXIssue,SOXIssue|SOXTask generates Business Entity - Issue and Business Entity - Issue - Action Item.