Configure self-contained object types

When you define an object type using the Self Contained Object Types setting, the behavior of that object type changes for copy, move, and rename operations.

A self-contained object type is an object type that has its own folder and is either part of the role-based security model as defined in the Model setting or defined using the Self Contained Object Types setting.

For information about the Model setting, see Role-based security model.

Note:
  • Roles can only be assigned to objects that are defined as security context points through the Model setting.
  • Defining an object type through the Self Contained Object Types setting does not automatically change the folders of existing instances of that type. If instances of the object type you want to define as self-contained already exist, you must contact IBM® Support for assistance in executing a special PL/SQL script that will go back and create folders for existing instances. This script is maintained by IBM OpenPages® Customer Services & Support and does not ship as part of the product. Conversely, if an object type is later removed from the self-contained list, no automatic re-foldering occurs. All existing instances retain their dedicated folders.

By default, Business Entities are self-contained objects. For example, if the role-based security model setting is defined as SOXBusEntity/SOXProcess, both Business Entity and Process objects are treated as self-contained objects.

Self-contained object types behave differently than non-self-contained object types for copy, move, and rename operations. The characteristics that distinguish self-contained objects from non-self-contained objects follow.

Self-contained objects:

  • Are always created under a parent folder that matches the object name (the same behavior as Business Entities). For example, a process P1 under the North America business entity will have the path /North America/P1/P1.txt
  • When copied, all the objects under its hierarchy will also be copied to the target.
  • When moved, all the objects under its hierarchy will also be moved to the target.
  • Can have only one parent of the same object type.
  • Can only be moved to an allowed parent object.
  • Cannot be moved to a folder.
  • Cannot have their parent folder edited, moved, or renamed.
  • Can be renamed by users who have Read and Write access control (ACLs) permissions.
  • During a copy operation, if a naming conflict exists between the source and the target object, the copy operation will fail and the naming conflict resolution choices made by a user are ignored.
Common > Self Contained Object Types
Default: none.
Values: In the Value field, type a comma-separated list of object type names.

For example, if you wanted Process and Risk Assessment object types, you would type: SOXProcess,RiskAssessment.

Applications > Common > Administration > System Files > Show GRC Folder Structure
Default: false
Values:
  • true - _op_sox folder and subfolders are displayed
  • false - _op_sox folder and subfolders are not displayed

Controls whether the GRC Object folder structure and system files are displayed in the Open Administration menu Administration menu > System Configuration > System Files task.