Clarity
Studio Partitions

ccppmop159
To create different views of the same objects for different users, you can use
partitions
. Your users are likely not using every field on every page in the application. You can simplify the user interface by defining what can be viewed in a partition. You can give a user or a group of users access to one or more partitions. You can set up partitions by department, geography, industry, division, legal structure, or any other method that your enterprise requires.
This explanation of partitions assumes the items that you want to include in the partition (for example, objects or attributes) exist. This explanation does not explain how to create items to include in the partitions.
Partitions are an optional way to manage and extend the presentation of information. They are not required as part of the product setup.
A
partition model
is the top node (parent) of a partition hierarchy. All partition models belong to the System partition, the default product partition. You can create a partition model to fit any structure that your enterprise needs. You can add as many partitions as necessary to a partition model. You can also add partitions to partitions so that you can create a multilevel hierarchy if necessary. Each partition can contain its own version of information that is specific for its environment.
Example: A Partition Model
The following image shows a simple partition model. An administrator creates partition A for global company operations. Partition A has child partitions for regions in the USA (B) and Europe (C). The European partition (C) has two child partitions for offices in London (D) and Paris (E). The partitions contain project object attributes that are specific to those office locations. The administrator adds custom attributes to the
project
object and assigns them only to the appropriate partition. The functionality and other aspects of the project object are shared across all users with the appropriate access rights. However, specific view settings are available only to users who are assigned access to those partitions.
Image showing a simple partition model
Image showing a simple partition model
The following table shows how you can customize the content items in each partition.
Content Items
A: Global
B: USA
C: Europe
D: London
E: Paris
Attributes
Processes
Lookups
Portlets
UI Theme
Views
Links
Review Partition Prerequisites
Review the applicable prerequisites in this list:
  • Enable the following access rights:
    • Administration - Studio
    • Administration - Partition Models
  • Identify the number of partitions needed.
  • Identify the hierarchical structure of the partitions.
  • Determine what to include in each partition.
  • Identify the users for each partition. Users can be assigned to only one partition. This single partition assignment means that they do not have to select a partition. A user who is a member of more than one partition must select a default partition in their account settings so that the application will render views and data properly.
  • Consider the following rules when planning your partitions:
    • You can set up multiple partition models.
    • An object can be assigned to only one partition model at a time.
    • When an object is assigned to a partition model, default associations apply. For example, attributes, views, and links are visible to all partitions in the partition model.
    • When you include a partition in a partition model, its location in the hierarchy is fixed. You cannot move the partition.
    • You cannot delete a partition model; however, you can deactivate it.
    • A child partition can inherit what can be viewed in its parent, depending on the association mode selected. If the child partition has been modified, changes to the parent partition are not applied to the child partition.
    • A user who is not a member of any partition sees the default System partition views.
    • A user with Studio access rights can be a member of more than one partition in a partition model. However, when the user creates an object, the user selects the partition to use. For example, a user can be a member of two partitions. The user selects one partition to use when creating a project.
    • You can export partition models and other items that are created during partitioning. Use the XML Open Gateway (XOG). When you export a partition model, only the partition model and its partitions are exported. Any objects or other settings that are associated with the partition are not exported.
    You do not need to restart the product to enable partitioning; all partitioning configuration changes are immediately available.
Create a Partition Model and Add Partitions
Create a partition model and add a partition for each different presentation of the user interface your enterprise requires.
Follow these steps:
  1. Click Administration, Studio, Partition Models.
  2. Click New and specify the required information.
  3. Click Save and Continue.
    The Partitions tab is activated. You can add partitions to the new partition model.
  4. Click New.
    To add multiple partitions to the new partition model simultaneously, click Quick Create.
  5. Enter the information for the new partition.
    • Parent Partition
      Specifies the position of the new partition in the hierarchy by identifying the parent partition.
    • UI Themes
      Specifies the color theme for the partition user interface.
  6. Save your changes.
Associate Objects with a Partition
The Standard partition contains default objects that are associated with all partitions through inheritance. This procedure explains how to associate a custom object with a partition. You do not have to be a member of a partition to perform this task. An object can be associated with only one partition model.
Follow these steps:
  1. Open Administration, and from Studio, click Objects.
  2. Click the name of an object.
    The properties page appears.
  3. Select a partition model.
  4. Save your changes.
Include Attributes in a Partition
Create attributes to collect specific information. For example, the London office of an enterprise has different project requirements than the Paris office. The administrator creates attributes for the project object that are specific to the London office and includes them in the London partition. Only the users who are included in the London partition see the attributes.
You can change the partition assignment or partition mode of an attribute at any time. Carefully consider the impact that changes can have on items that reference an attribute. For example, a grid portlet using a user-defined date attribute for Gantt chart columns does not display if the required date attribute becomes absent. A process instance can fail if it can no longer evaluate or set an attribute.
Follow these steps:
  1. Open Administration, and from Studio, click Objects.
  2. Click the name of the object whose attribute you want to add to a partition.
  3. Click Attributes to display the object attributes.
  4. Click the attribute that you want to assign to a partition.
  5. Complete the following fields:
    • Partition
      Specifies the partition to associate with the attribute.
    • Partition Association Mode
      Specifies which partitions can include the attribute, in addition to the selected partition.
  6. Save your changes.
Modify Views for a Partition
Views determine how information displays in the product for a specific object. You can determine the attributes that display for the object and the arrangement of attributes on the page. Each object has the following default views:
  • Properties
    Lets a user enter information for an object instance. For example, the properties view for the project object lets a user enter information for a specific project.
  • List Column
    Displays the instances of an object in rows and columns.
  • List Filter
    Lets a user search for information about the list column page.
If a partition does not have views for an object, the partition inherits the object views of the nearest ancestor partition. If no ancestor partitions have views for the object, the partition uses the System partition views.
Best Practice:
Define partitioned views for objects at the top of the partition model first. For example, if you are using a geographical partition model with
World
at the top and
United States
and
Europe
as children partitions, define the World views first.
Follow these steps:
  1. Click Administration, Studio, Objects.
  2. Click the name of the object whose views you want to modify for a partition.
  3. In the object properties, verify that a partition model is assigned to the object.
    If a partition model is not assigned, assign the correct partition model to the object.
  4. Click Views.
    The list of views for the object appears.
  5. In the Partition field above the list, select the partition to which the view modifications apply.
  6. Use the view links to modify the layout of the object for the selected partition.
Include Object Links in a Partition
Include object links in a partition to provide shortcuts to subpages of the object page or to external web pages.
Follow these steps:
  1. Open Administration, and from Studio, click Objects.
  2. Click the name of the object whose link you want to add to a partition.
  3. Click Linking.
  4. Click the link that you want to assign to a partition.
  5. Complete the following fields:
    • Partition
      Specifies the partition to be associated with the object link.
    • Partition Association Mode
      Specifies which partitions can include the object link other than the selected partition.
  6. Save your changes.
Define Static Lookup Values for a Partition
You can partition static lookup values. Users of a partitioned lookup see different values in the lookup, depending on the partition to which an object instance belongs. Partitioned lookups allow you to enforce standard options throughout an entire branch of a partition model. You can also add lookup values to meet the unique requirements of a business unit partition.
You can add partitioned values to default static lookups or to user-defined static lookups. If an object instance is not partitioned, the lookup shows only values for the System partition. You can assign a lookup to a partition when you create it, or you can modify an existing lookup and then assign it to a partition.
Follow these steps:
  1. Open Administration, and from Data Administration, click Lookups.
  2. Click a static lookup.
  3. Click Values to see the values that are assigned to the lookup.
  4. Click the name of the value that you want to assign to a partition.
  5. Complete the following fields:
    • Partition
      Defines the partition for a lookup value.
    • Partition Association Mode
      Specifies which partitions can include the lookup value other than the selected partition.
  6. Save your changes.
Select a UI Theme for a Partition
A
UI theme
varies the look of the user interface. Default UI themes allow you to change the user interface colors, login information, branding, and other visual elements. Any custom UI themes can apply changes to the logo, the application name, tabs, buttons, icons, and other features.
When creating a partition, you can select a UI theme or you can accept the default theme. This procedure explains how to select a UI theme after you create a partition.
Follow these steps:
  1. Open Administration, and from Studio, click Partition Models.
  2. Click the name of the partition model.
  3. Click Partitions.
  4. Click the name of the partition for which you want to set the UI theme.
  5. Select a UI theme.
  6. Save your changes.
Test the Partitions
When a partition is complete, test it in the product user interface. Testing verifies that all of the information that you want presented in the partitions is available.
Follow these steps:
  1. Create a test user with the appropriate access rights and assign the user to the partition.
  2. Log out as a user with Studio access rights and log in to the product as the test user.
  3. Verify that the modifications that you made to the partition are available.
  4. Repeat this procedure for each partition.
Assign User Access to Partitions
Access rights determine what information users can see and the functions they can perform. The administrator can grant access rights to users (resources), groups, OBS units, or globally to all users. Partitioning affects what objects are exposed to users. Therefore, partitioning and access rights work together.
If a user has access rights to an instance of a partitioned object, the user can see partitioned views of the instance. The user can see the instance even if the user is not a member of the partition to which the object instance belongs.
Partitioning affects user ability to do the following tasks:
  • Create partitioned attributes.
  • Change the layout and appearance of attributes for partitioned objects.
  • Assign an object instance to a partition.
  • Select a default partition.
  • Switch partition views.
  • See and personalize partitioned List Column and List Filter views.
  • Create or see partitioned values for lookups.
Follow these steps:
  1. Click Administration, Studio, Partition Models.
  2. Click the name of a partition model.
  3. Click Partitions.
  4. (Optional) Click the + icon next to a partition to see child partitions.
  5. In the row that contains the partition you want, click the Properties icon.
  6. To assign an individual user (resource), a group, or an OBS unit access to the partition, complete the following steps:
    1. Open the Partition Members menu and click one of the following menu options: Resources, Groups, or OBS Units.
    2. Click Add.
    3. Select the appropriate check boxes and click Add.
      If you have more selections than appear on a single selection page, use Add and Select More.
  7. After you add all selections, click Return.
    You have completed the configuration of partitions.