Navigation From and To Person
The Person business objects are a hierarchical collection of several child business objects, each of which holds specific details about a person.
The Person business objects hierarchy includes the Person business object at the highest level in the hierarchy followed by other Person child business objects that hold personal details in a 1 to 1 relationship with the person. For example, the Passport business object holds info about 1 or more passports of a person, the Citizenship business object holds 1 or more citizenship entries for a person, and so on. The Person business object names easily help you identify the business object you need to validate.
This section lists the business objects you can navigate to and from the Person business object. The only type of rule Person business objects support is Object Validation. The Person business objects don't support default or field validation rules.
Typically, the starting point is the Person business object containing the field to be validated, but not always. While it may seem like for a given use case we are validating the email address or the national identifier, you need to further analyze your requirement in detail for what you're validating and what's the validation criteria.
For example,
-
If your requirement is to validate the format of an attribute such as the national identifier, address line 1, last name, phone number, and so on, related to just one record, then you need to start with the corresponding child business object.
-
If your requirement is that a person must have at least one national identifier or the criteria is having one or more national identifiers of a certain type or not, you need to start with the Person business object instead of the Person National Identifier business object. You can always traverse to any other Person business object to sample its values when you're in another business object.
From Other Business Objects to Person
To access the Person business object, use the row variable (variant 2) Get Person from any business object.
Consider the following information when navigating to the Person business object.
|
From Business Object to Person |
How |
Purpose |
|---|---|---|
|
Worker Assignment |
row variable (variant 2) |
To check for attributes of Person and then from there other children business objects of Person with additional row variable declarations. |
|
Worker Work Relationship |
row variable (variant 2) |
To access the Person business object, you need to access it through the Worker Assignment business object. To check for attributes of Person and then from there other children business objects of Person with additional row variable declarations. |
|
Any Person Child Business Object for example, Person National Identifier |
row variable (variant 2) |
When navigating to the Person business object from any of its own children, you need to use the row variable variant 2. |
|
Person Contact Relationship |
row variable (variant 1) |
When working with the Contact Relationship business object you have two options (both row variables of Variant 2) to access either, the Person or the Contact Person. The Person ID on the Person Contact Relationship business object is the Person ID of the worker. The Contact Person ID is the Person ID of the contact. For example, if you want to access Contact B's (who's a contact of Worker A) record, you need to go to the Person Contact business object instead of the Person business object. But, if you want to access Worker A's record, you need to go to the Person business object instead of the Person Contact business object. |
To Other Business Objects from Person
Consider the following information when navigating from the Person business object.
|
From Person To Business Object |
How |
Row Variable |
Purpose |
|---|---|---|---|
|
Worker Assignment |
row variable |
Get Assignment |
You must use caution when accessing the Worker Assignment business object because it fetches all assignments for all work relationships of a person. You can use only rowset declaration, if it's appropriate. After accessing Worker Assignment, the rest of your rule needs to be encapsulated under the "If WorkTermsAssignmentId NOT NULL" condition. This, even before you declare any further row variables from Worker Assignment or use any of its fields. You need to iterate over each assignment record to determine your match, for example, primary assignment. You may find multiple primary assignments depending on how many work relationships you allow in your organization. You need to use the Get Assignment view accessor to get all assignments. This isn't applicable for people who are only contacts because they don't have a worker assignment. |
|
Any Person Child Business Object |
rowset variable |
|
One person record can have multiple records within a Person child business object. For example, Worker A can have a US and a UK national identifier record. When navigating from Person to the child, you may need to declare a rowset variable to iterate over the children rows to detect your condition. |
|
Person Extra Information |
rowset variable |
Get Person Extra Information |
This is to iterate over all Person Extensible Flexfields (EFF) context rows for a given person in a subsequent row collection looping block. Use the Get Person Extra Information view accessor to access a set of records from the Person Extra Information business object displayed in Autocomplete Rules for a specified person ID. |
|
Person Profile Education and Person Profile Certification |
rowset variable |
Get Profile |
Use the Get Profile view accessor to traverse from the Person business object to the Person Profile Education and Person Profile Certification business objects. For example, you can validate the education degree or certification validity, or both when promoting your worker. |