Create Work Relationship

This topic lists the implementation considerations for the Create Work Relationship process.

You can typically use field value defaulting and validation in these cases.

• Default the enterprise seniority date from the most recent employee work relationship if any of the previous assignments are employee records. In case of nonemployees, with no previous employee record. then use the action date of the hire for enterprise seniority date.
• Default job, assignment category, hourly/salaried, FTE, and working hours for a primary assignment of a primary work relationship when a new assignment is added for an employee or contingent worker.
• Validate that an employee isn't rehired as an hourly employee within 13 weeks of his last termination date as a full time (Validate ValiSalaried) employee. This restriction should not be applied on below cases:
  • Salaried employee is rehired as Salaried employee
  • Hourly employee is rehired as Salaried employee
  • Hourly employee is rehired as Hourly employee
• Validate that if the user person type is Jobstudents and new hire date is < 1 month to the last termination date. In such case, the error displayed is "Jobstudents cannot have a new contract less than one month after the old contract".

This table lists the supported attributes, exceptions, and the implementation recommendations for the Create Work Relationship process.

It applies to pages under My Client Groups tab.

In the Conditions to Default Field Values	To Default Field Values	In the conditions to Validation Field Values	To Validate Field Values	Implementation Guidelines
Reference Objects supported in conditions Job Job DFF Job EFF Job Family Job Family DFF Location Location EFF Grade Grade DFF Department Department DFF Department EFF Legal employer EFF Position Position Valid grades Position EFF Position DFF Grade Ladder Grade Ladder DFF Grade Step Action Action DFF Action Reason Action Reason DFF Worker - To get the previous existing work relationship and assignment data Logged in Person Assignment	Sections that support Defaulting When and why (actionOccurrences) Assignment (addPersonWorkRelationships) Work relationship Info Additional assignment info Fields in When and why section that support defaulting Action Action Reason Effective date Business Unit Position Legal employer Worker Type	Reference Objects supported in conditions Job Job DFF Job EFF Job Family Job Family DFF Location Location EFF Grade Grade DFF Department Department DFF Department EFF Legal employer EFF Position Position Valid grades Position EFF Position DFF Grade Ladder Grade Ladder DFF Grade Step Action Action DFF Action Reason Action Reason DFF Worker - To get the previous existing work relationship and assignment data Logged in Person Assignment	All fields in these sections: When and why (actionOccurrences) Assignment (addPersonWorkRelationships) Work relationship Info Additional assignment info	Assignment section fields not supporting defaulting Default Expense account People Group Flags like Primary assignment flag, Primary work relationship and Primary flag Business Unit and Legal employer as they are taken from When and why Assignment Notes Assigment Type Standard working hours and frequency Synchronize from position Flag

Considerations for Implementing Create Work Relationship

• 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.