Add Person

This topic lists the implementation considerations for these Add Person processes.

• Add a Contingent Worker
• Add a Nonworker
• Add a Pending Worker
• Edit Pending Worker
• Convert Pending Worker
• Hire an Employee

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

• Default projected end date 12 months from the start date.
• Default grade to the last grade the person was tagged when they left the organization in case of rehire within 1 year of previous exit.
• Validate business title string to only include ASCII characters.
• Validate proposed start date for a worker to be within next 3 months.

This table lists the supported attributes, exceptions, and the implementation recommendations for the Add Person processes.

It applies to the processes accessed from these tabs.

• Add a Contingent Worker - My Team and My Client Groups
• Add a Nonworker - My Team and My Client Groups
• Add a Pending Worker - My Team and My Client Groups
• Convert Pending Worker - My Client Groups
• Edit Pending Worker - My Client Groups
• Hire an Employee - My Client Groups

In the Conditions to Default Values	To Default Field Values	In the Condition to Validate 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 Department, Department DFF Department EFF Legal Employer EFF Position., Position Valid Grades Position EFF Position DFF Grade, Grade DFF Grade ladder and their respective flex fields Trade Ladder DFF Grade Step Action Action DFF Action Reason Action Reason DFF Logged in Person Assignment	When and Why fields supported for defaulting Action Action Reason Effective Date Business Unit Position Legal Employer Worker Type 2. All assignment section fields except Contract fields Default Expense account People Group Primary flags for Assignment or Work Relationship Business Unit and Legal Employer as they are taken from When and why Assignment Notes Assignment Type Standard Working Hours and Frequency Synchronize from position Flag	Reference Objects supported in conditions: Job, Job DFF Job EFF Job Family Job Family DFF Location, Location EFF Department, Department DFF Department EFF Legal Employer EFF Position., Position Valid Grades Position EFF Position DFF Grade, Grade DFF Grade ladder and their respective flex fields Grade Ladder DFF Grade Step Action Action DFF Action Reason Action Reason DFF Logged in Person Assignment	All assignment fields	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 can't be done in 25B 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 can't be done in 25B. This will be supported in a later release. Any defaulting and validation based on position incumbent count aren't supported in 25B. 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 multi row sections supported regions isn't supported currently.

Note:

Refer to Change Assignment for tips and considerations for the Edit Pending Worker process.