Configure data segmentation

• The Manage Data Segmentation controls data segmentation. Support assigns it to customers who want to use data segmentation. You also need the Manage Key Properties privilege, which you get that automatically when your session starts.

1. From the navigation bar, click Administration>Key Properties.
2. From the Manage Key Properties page, click Add Category.
3. From the drop-down menus, select the Category and Alias to use for data segmentation.
4. Click Done.

   Note: This key property will ultimately be required, however depending on how many users/processes are creating user in the client installation, it may not be practical to set it to be required at this time. The selected category alias must also be part of every event definition as a category or required attribute. This is enforced later in the process. At the point of defining the key property, the application does not enforce the above but does later in the process (see below).

5. Click Update Categories.

   Note: To configure a selected category alias as the data segmentation category, all employees must have a value for the corresponding key property.

6. Select the Required check box of the category you want to enable data segmentation.
7. Select the Data Segmentation check box of the same category.
8. Click Update Categories.

Processing notes and rules

• After making a category required, the data segmentation check box for that category is enabled. When un-requiring a category, the data segmentation check box for that category is disabled and unselected. You cannot un-require the data segmentation category. The application disables the Required check box for the data segmentation category.
• Administrators can check the box in the data segmentation column for, at most, one of the required categories.
• When an administrator selects a category as the data segmentation category, the application verifies whether all:
  • Employees have a key property category value for this category. (This is possible if the key property was just defined or just made required when it was not previously). If not, a warning message appears, alerting you that not all employees have key property category values set.
  • Event definitions have the category as an event category or required attribute. If not, a warning message appears and you are prompted to add the category as an attribute to all events and set the value for the event attribute to the value of the "for whom employees" corresponding key property.

  Tip: You can choose to cancel this process. However, at this point, all employees should have key property values, so best practice is to add the attribute and set its value.

  The category alias is added as an event attribute only to events that do not have the selected category and set its value for all Work Events to the value of the “for whom employee’s” corresponding key property.

  Note: If there are event definitions that have the category as an event attribute that is NOT required, the application makes it required and sets its value for all Work Events (that don’t have a value) to the value of the “for whom employee’s” corresponding key property.

• The Data Segmentation category cannot be deleted:
  • On the Manage Key Properties page, the Data Segmentation Delete check box is disabled once selected.
  • On the Manage Event page for all event definitions, the Required check box and Remove button for the event attribute and event category corresponding to the data segmentation category are disabled.
  • When creating a new event definition, the data segmentation category must be defined as an event category or required event attribute.
• A read-only notes section is available on the Manage Key Properties page. Users with the Manage Data Segmentation privilege can view it.
• System notes are added in this section for every change to data segmentation configuration.