Variable Pay template having two pay components

[DavidSomelofske]

In our Variable Pay template, we have two distinct employee groups: out of 10,000 total employees, 4,000 must publish to pay component 4100, while the remaining 6,000 must publish to pay component 4110. While I can identify these groups using a custom reportable field to control user publishing, the standard UI does not allow us to dynamically select the target pay component. The only apparent solution is to manually update and upload the XML template via Provisioning for each group. However, because the client will not have Provisioning access or XML expertise after go-live, we need an alternative approach to handle this pay component differentiation without modifying the XML post-implementation.

[DavidSomelofske]

If you create the configuration for the client during the implementation, they can adjust the publishing by adjusting the xml and using the update template functionality.

[DavidSomelofske]

there is a cloud emoji in the compensation home template list by clicking this, they can update the file without provisioning, however, the changes need to be done prior to the forms being launched.