Local and Global Transfer
This topic lists the implementation considerations for the Local and Global Transfer process.
You can typically use field value defaulting and validation in these cases.
- Default reporting establishment on the Employment Details page based on location EFF mapping.
- Default work at home to Yes if the work arrangement DFF is set to Onsite. Default the Work at home field to No, if the work arrangement DFF is set to Remote.
- Validate Assignment Name/Business title changes limit to 50 characters
- Validate employee's legal employer and department
This table lists the supported attributes, exceptions, and the implementation recommendations for the Local and Global Transfer process.
It applies to both pages under My Team and My Client Groups tabs.
In the Conditions for Defaulting | To Default Field Values | In the Conditions for Validation | To Validate Field Values | Implementation Guidelines |
---|---|---|---|---|
Reference Objects supported in conditions
|
Sections supporting default
|
Reference Objects supported in conditions
|
Assignment Section fields Not Supporting defaulting
|
Considerations for Implementing Local and Global Transfer
- Any defaulting or field validation rule that needs to be done based on UDT (user defined table) can't be done in Business Rules.
- Contract section related defaulting and validation isn't currently supported for Add Person flows, Create Work Relationship, Convert Pending Worker, and Local and Global Transfer. This will be supported in a later release.
- Any defaulting or validation of the transaction dates based on payroll periods isn't currently supported. This will be supported in a later release.
- Any defaulting and validation based on position incumbent count isn't currently supported.
- Person sections that support multiple rows and those that have any cross rows validations need to be done in ADF Autocomplete. Validation in Business Rules isn't supported.
- For multiple row sections, cross row validation isn't possible for person sections.
- For validations in other sections based on the rows in the multirow sections supported regions isn't possible currently.
- For object-level validation, it's recommended to use the ADF Autocomplete rules.
- The ADF Autocomplete rules for all the add flows will trigger on clicking Submit and not on Continue.