Person: Exceptions and Adaptations

This table lists rules that can't be currently implemented for the Person business object.

Exceptions

Rule	Rule Type	Actions Impacted	Sections Impacted	Fields Impacted	Comments
Set default on entry into section, set default on tab-out and validation on tab-out not supported	Object Defaulting, Field Modification, Field Validation	All	All	All	N/A
Person Legislative Information business object validation is triggered before entry into the Person Legislative Information section	Business Object Validation	All applicable Employment Actions	Person Details, Legislative Info	All	You may sample a mandatory field of the Legislative Info section for null value to determine when to trigger the validation. The Legislative Info is validated once when exiting the Person Details section and again after exiting the Legislative Info section.
Person Legislative Information business object validation doesn't trigger after the Legislative Information section, if a predefined field isn't modified	Business Object Validation	All applicable Employment Actions	Legislative Info	All	N/A
Can't determine context of addition or change in the absence of When of Why section	Business Object Validation	All applicable non-Employment Actions	Any Person related section	All	The rule will trigger regardless of where this business object is being used. For example, if you want to validate a contact type in the Benefits People to Cover page, but not the Global HR Family and Emergency Contacts page, there's no way to restrict this validation to only the People to Cover page. In some cases, the user role may be used as a proxy for when this addition or change occurs.

Adaptations

This table lists rules where you can vary the rule logic to achieve the result.

Rule	Rule Type	Actions Impacted	Sections Impacted	Fields Impacted	Comments
May not use Effective Date fields directly on the business object for date validations	Business Object Validation	All	All	All	Must use ChangeDate HCM Params for sampling effective dates of any Person related business objects. Doesn't apply to other non-effective dates like, issue date, expiry date, and so on.
Cannot traverse to When and Why business object to determine any field value entered in the When and Why section.	Business Object Validation	All applicable Employment Actions	Any Person related section	All	Must use HCM Params to determine state of values in the When and Why section.
Validating presence or absence, or both of Person children business objects like Passport, Drivers Licenses, NID, and so on	Business Object Validation	All	Person Details	All	Identify the section and the sequence in the page where it occurs. You can always start validation in a given business object, navigate up to the parent Person business object and then navigate back into another child business object of Person. For example, to ensure citizenship is entered prior to passport, you may write the validation on the Person Passport business object, navigate back up to Person and then navigate down to the Person Citizenship business object iterating over it to detect presence/absence. But in a new hire flow, where Passport is asked for prior to Citizenship, this kind of validation will lock you and prevent you from proceeding.