In the Customizations workspace, existing fields can be relabeled or deactivated, and custom fields can be activated.
During implementation, once you have determined which fields will be populated from incoming data, activate Generic Attributes, or custom fields, to receive the data.
In the Customizations workspace, you can:
- Relabel an existing attribute. For example, relabel the Participants workspace to Payees or Brokers.
- Create additional classifier types. For example, create a classifier type called Industries
- Indicate fields as Personally Identifiable Information (PII) to comply with data privacy regulations. For example, a generic attribute on the Participant record contains the employee’s street address. This can be set to sensitive PII to ensure this information is purged according to the organization’s requirements.
- Manage and create generic (custom) attributes. For example, each Participant has a Sales Status that affects their bonus amount. A generic attribute called GA1:Sales Status is created to hold this value.
- Change the attribute label using the Custom Value column. For example, the organization refers to the Position as the Job Code. The Position Name attribute can be relabeled to Job Code to reflect the business language.
- Customize labels for different languages and locales. For example, many users on the compensation team are in Latin America and prefer to use the system in Spanish. A Spanish locale can be created, and the attributes can be further customized to reflect the business terms.
- Add extended attributes. For example, if all generic attributes are used, more attributes can be added activating Extended Attributes. Because the use of Extended Attributes can affect processing time, use the default generic attributes first, especially if these attributes will be used in rule calculation.
All workspaces have four types of attributes:
- Generic Attributes (GA) – fields that contain text entries
- Generic Numbers (GN) – fields that contain only numeric entries
- Generic Dates (GD) – fields that contain date entries
- Generic Booleans (GB) – fields that contain Boolean entries (True/False, Yes/No)
Best Practices for Customizations
- Always check to ensure that the necessary locales are defined in the System Preferences dialog before customizing.
- If possible, avoid using extended attributes. Extended Attributes can affect processing time, use the default generic attributes first, especially if these attributes will be used in rule calculation.
- Keep in mind that custom Classifier Types cannot be deleted, so be careful when creating them.
