Configure Business Rules for Individual Compensation Processes

Use the following list to quickly identify the appropriate template rule for your defaulting and validation needs, and then configure it to match your organization’s requirements.

Defaulting Rules

Template Rule Name for Defaulting	Rule Description
Default Action Date to Next Payroll Period Start Date	This sample rule defaults the Action Date with the Next Payroll Period Start Date and marks the field as read-only.
Default Exclude Plans Based on Grade	This sample rule restricts a set of plans based on the employee's Grade. The Exclude Plans and Exclude Options value expects a JSON array of Plan IDs and Option IDs, respectively, as strings. To exclude a plan with ID 12345, the value for Exclude Plans should be ["12345"]
Set Add, Edit and Delete as Hidden based on role	This sample rule hides the Edit and Delete actions based on the logged-in user's role
Default Input Values by Individual Compensation Plan Option and Legislative Data Group	This sample rule defaults element input values for a specific individual compensation plan, option and legislative data group.
Default Input Values by Element	This sample rule defaults element input values for a specific element associated with the individual compensation plan option. Note that this method is more performant.
Default Input Values Based on Business Unit	This sample rule defaults element input values based on the business unit. The rule condition identifies the target element, and the business unit logic is defined as an advanced expression in the defaulting step.
Default Plan Start Date Based on Next Payroll Period Start Date and Country	This sample rule defaults the plan start date to the next payroll period start date. If the payroll period start date is unavailable, the start date is defaulted to next Monday for US legislation, or to the first day of the following month for all other legislations. Additionally, the field is marked read-only. The date computation is based on the effective date of the flow.
Default Plan End Date to the End of the Year	This sample rule defaults the plan end date to the end of the year. The date computation is based on the effective date of the flow.

Validation Rules

Template Rule Name for Validating	Rule Description
Validate Action Date within given date range	This sample rule validates the Action Date is within the given range. If the When section is enabled, this rule will be triggered on changing the value in the Action Date field. If the When section is hidden, the action date is same as the effective date and this validation rule will trigger on selecting Continue or Submit from the Compensation section. The rule trigger can be restricted to the When section by selecting Action Date in Message Target Fields.
Validate Start Date of a new claim	This sample rule validates the Plan Start Date value of a new allocation. This is a record level validation and is triggered on selecting Save in the allocation drawer. The Start and End Date fields are available as string in ISO date format (YYYY-MM-DD). For date operations, the value should be converted to date object using Advanced Expressions.
Validate Plan End Date with payroll period end date	This sample rule validates the Plan End Date of an allocation during edit operation. This is a record level validation and is triggered on selecting Save in the allocation drawer. The Start Date, End Date and Payroll Period Start Date fields are available as string in ISO date format (YYYY-MM-DD). For date operations, the value should be converted to date object using Advanced Expressions.
Validate Primary Input Value of a new allocation	This sample rule validates the Amount (the primary input value) of a new allocation. This is a record level validation and is triggered on selecting Save in the allocation drawer. The value field of individualCompensationDetails object holds the value of the primary input field in string format. For arithmetic operations, the value should be converted to number using Advanced Expressions.
Validate new allocation by Grade	This sample rule validates the allocation of car allowance based on employee's Grade. This is a record level validation and is triggered on selecting Save in the allocation drawer.
Validate Primary Input Value of an allocation during update	This sample rule validates the Amount (the primary input value) of an allocation against the initial value during update operation. This is a record level validation and is triggered on selecting Save in the allocation drawer. The value field of the individualCompensationDetails object holds the primary input field in string format. For arithmetic operations, the value should be converted to number using Advanced Expressions. Note: During date effective update, the record object will have Operation value as SPLIT, and and the initial value (which is the end-dated reocord) will have Operation value as PRE_SPLIT.
Validate Start Date of a new allocation against prior allocations	This sample rule validates that the start date of a new allocation is not within 6 months of the last allocation of the same plan. This is a record level validation and is triggered on selecting Save in the allocation drawer. The Prior Allocations field holds the information of all the inactive allocations as of the effective date. This field is an array of objects where each object is a allocation record. To access the details of each allocation, iterate the Prior Allocations field using Advanced Expressions.
Validate more than one new allocation in a transaction	This sample rule validates the presence of multiple new allocations in a transaction. This is a section level validation and is triggered on selecting Continue or Submit or the flow level Save button. The Current Allocations field holds the information of all the active allocations as of the effective date. This field is an array of objects where each object is an allocation record. To access the details of each allocation, iterate the Current Allocations field using Advanced Expressions.
Validate viability of multiple allocations	This sample rule validates the viability of multiple allocations. In this example, allocation of both car allowance and taxi allowance is restricted. This is a section level validation and is triggered on selecting Continue or Submit or the flow level Save button. The Current Allocations field holds the information of all the active allocations as of the effective date. This field is an array of objects where each object is an allocation record. To access the details of each allocation, iterate the Current Allocations field using Advanced Expressions.
Validate absence of a plan by Job	This sample rule validates the absence of a plan by employee's Job. This is a section level validation and is triggered on sleceting continue or submit or flow level save button. The Current Allocations field holds the information of all the active allocations as of the effective date. This field is an array of objects where each object is a allocation record. To access the details of each allocation, iterate the Current Allocations field using Advanced Expressions.
Validate Input Values	This sample rule validates the input values for an ICP award. It runs as a record-level validation when the user clicks Save in the allocation drawer. The Input Values field contains an array of BaseName and ScreenEntryValue pairs that you can reference in conditions, and you can combine them with other fields and contexts for more advanced conditions.