Custom Compensation Statements
Custom compensation statements enable administrators to create templates for compensation statements to add to compensation planning tasks. Custom compensation statements use tags to embed User, Compensation, Performance, and Competency fields into the compensation statement.
The WYSIWYG (what you see is what you get) tool enables administrators to use images, fonts, colors, formatting, tables, etc. There is also a Copy from Word feature, which enables administrators to import from Microsoft Word, preserving the formatting used in the Word document. HTML code can also be used in the editor.
Administrators can create conditional sections within the custom statement, which allows the administrator to include or exclude specific content based on user-specific data.
Once a custom compensation statement is created, administrators can add the custom statement to a compensation planning task. Once the task is complete, all users in the task have their compensation statements based on the selected custom statement template. If a custom compensation statement is not applied to a planning task, then the standard compensation statement is used.
Custom compensation statements support localization and currency conversion, based on the user's settings.
To manage Custom Compensation Statements, go to.
|PERMISSION NAME||PERMISSION DESCRIPTION||CATEGORY|
|Compensation Custom Statements||Grants ability to create templates for compensation statements to add to compensation planning tasks. This permission cannot be constrained. This is an administrator permission.||Compensation - Administration|
To create a custom compensation statement, click the Create Custom Compensation Statement link. See Custom Compensation Statement - Create.
To search for an existing custom statement, enter the name of the custom statement in the Name field and click the Search button.
Select the Display Inactive Statements option to include inactive statements in the display.
The Statements table displays the following information for each custom statement:
- Statement Name - The name associated with the custom statement.
- Last Updated - The date on which the statement was last updated.
- Last Updated By - The user who last updated the statement.
- Active - Select this option to make the statement active. When a statement is inactive, it is not available for future planning tasks unless it is already associated with the task. Tasks that are deployed, started, or completed are not affected.
The following options are available for each custom statement:
- Edit - Click this icon to edit the custom statement.
- Copy - Click this icon to copy the custom statement.
- View Details - Click this icon to open a pop-up, which displays all of the planning tasks (completed, expired, inactive, active, in progress, etc.) that use the custom statement.
- Delete - Click this icon to delete the custom statement. Note: This option is only available for statements that are not associated with any planning tasks. Once the statement is added to a task, this option is not available.