With partitions, you can create local configurations of Clarity that have their own forms, fields, processes, branding, and security rules.
You can govern globally by defining fields at the top of your organizational hierarchy and then make them required for every object instance throughout Clarity. Manage locally by deploying fields directly to child (descendant) partitions so that only child partitions must supply values for a field.
Follow these basic guidelines when working with partition models:
- Once you set up a partition you cannot move it, not even within the same level.
- You cannot delete partition models-you can only deactivate them.
- You can set up more than one partition model within CA Clarity PPM.
- An object can only be assigned to one partition model.
Overview of the partitioning process:
- Plan your partitioning implementation on paper so that you can carefully consider the impact to users.
- Set up a partition model.
- Select an existing object to use or create a new object.
- Add fields to the object, assign them to a partition, and select a partition association mode.
- Configure the views for each partition.
The following steps are optional:
- Add partition-specific object links.
- Create new UI themes and associate them with your partitions.
- Create partitioned lookup values.
- Create portlets based on partitioned objects.
- Create processes.
To work with partition models, you will need Studio - Access,
Partition - Administrator and preferably System Partition - Administrator access rights.
Note: You do not need to restart Clarity to enable partitioning
- all partitioning configuration changes are immediately available.
You can also transfer partition models and other items created in connection with partitioning from Clarity using the XML Open Gateway (XOG).