Personal Details rules for Add flows
Now you can write rules in employment add flows for the collection of rows use cases for person objects such as AllPersonAddress, AllPersonNationalIdentifiers, and AllPersonNames. in VB Studio to define your business rules for the following flows:
- Hire an Employee
- Add Contingent Worker
- Add Pending Worker
- Add Nonworker
- Convert Pending Worker
- Edit Pending Worker
- Local and Global Transfer
- Create Work Relationship
Scope of personal details
- Covers the Personal Details functional areas exposed by Person REST, such as biographical information, national identifiers, contact and demographic attributes, and other supported sections that appear in the Personal Details task of Core HR.
- Enables extension of these sections (for example via flexfields) to be surfaced and managed through the flows because the feature leverages the standard REST representation of the person record.
Now you can create business rules for use cases such as:
- Validation rule assuring that Spanish citizens not allowed to add NIE (Número de Identidad Extranjero AKA Foreigner Identity Number - If the employee selects that they have Spanish citizenship, they're not allowed to add an NIE (Número de Identidad Extranjero AKA Foreigner Identity Number).
- Validation rule to prevent creatio of work email in case of hire an employee operation Prevent creation of more than one home email in case of hire an employee operation - if operation is hire an employee and Work Email Address is not Null then Error if operation is hire an employee and There is more than one home email then error
- Defaulting rule to default PER_PERSON_LEGISLATIVE_DATA_LEG_DDF ATTRIBUTE1: Hijri Date of Birth by converting Date of Birth (Gregorian) to Hijri Number Date
- This feature standardizes how personal data (such as biographical, demographic, or identifiers) is created and updated across add-oriented person flows by routing those operations through the Person REST services instead of legacy service layers.
- It aligns VBCS UI and business rules with the Person REST payloads so that the same validations, defaulting, and extensibility options apply consistently across Hire, Pending Worker, Local and Global Transfer, and similar flows.
- For the abovementioned flows the UI now calls the Person REST endpoints to create or update the worker details as part of the overall transaction, rather than invoking older SOAP or internal APIs.
- This supports more consistent validation and error handling, simplifies technical uptake for future REST changes, and facilitates VBCS business rules or extensions that trigger on person-personal REST operations within these flows.
Steps to enable and configure
Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.
Tips and considerations
-
For Edit flows such as Edit or Convert PWK if the person object isn't included as a part of the flow, you should make sure that the user has a required aggregate privilege. For more information see section Access Requirements.
-
While the examples given above are for Hire an Employee, the similar business rules can be defined for all other flows that this feature applies to.
Key resources
For more information, refer to these resources on the Oracle Help Center.
- Extending HCM Redwood Pages Using Visual Builder Studio (VBS)
-
Extending HCM Redwood Applications Using Visual Builder Studio
Access requirements
| Resource Type | Business Object | REST Resource Name | Date efective (Y/N) | Usage | Required Access Privileges |
|---|---|---|---|---|---|
| Parent | Person | personalDetails (GetPerson) | N | Used for accessing biographical and personDFF data | Read Person Biographical Info Business Object (Required only if biographical data needs to be accessed) |
| Child | Person Addresses | AllPersonAddresses | Y | Used for accessing person addresses data which is valid on a given effective date | Read Person Address Business Object |
| Child | Person Citizenships | AllPersonCitizenships | N | Used for accessing person citizenship data | Read Person Citizenship Business Object |
| Child | Person Contact Relationships | AllPersonCitizenships | Y | Used for accessing person contact relationship data which is valid on a given effective date | Read Person Contact Business Object |
| Child | Person Details | AllPersonDetails | Y | Used for accessing person number | Read Person Business Object |
| Child | Person Driver Licenses | AllPersonDriverLicenses | N | Used for accessing person driver licenses data | Read Person Drivers License Business Object |
| Child | Person Email Addresses | AllPersonEmailAddresses | N | Used for accessing person email addresses data | Read Person Email Business Object |
| Child | Person Demogragphic Info | AllPersonLegislativeInfo | Y | Used for accessing person legislative info data on a given effective date | Read Person Legislative Info Business Object |
| Child | Person Demogragphic Info | AllPersonEthnicities | N | Used for accessing person ethnicities data | Read Person Ethnicity Business Object |
| Child | Person Demogragphic Info | AllPersonReligions | N | Used for accessing person religions data | Read Person Religion Business Object |
| Child | Person Expernal Identifiers | AllPersonExternalIdentifiers | N | Used for accessing person external identifier data | Read Person Identifier for External Applications Business Object |
| Child | Person Names | AllPersonNames | Y | Used for accessing person names data on a given effective date | Read Person Name Business Object |
| Child | Person National Identifiers | AllPersonNationalIdentifiers | N | Used for accessing person national identifier data | Read Person National Identifier Business Object |
| Child | Person Other Communication Accounts | AllPersonOtherCommunicationAccounts | N | Used for accessing person other communication accounts data | Read Person Other Communication Business Object |
| Child | Person Passports | AllPersonPassports | N | Used for accessing person passports data | Read Person Passport Business Object |
| Child | Person Phones | AllPersonPhones | N | Used for accessing person phones data | Read Person Phone Business Object |
| Child | Person Visas and Permits | AllPersonVisasAndPermits | Y | Used for accessing person visas and permits data on a given effective date | Read Person Visa Permit Business Object |
| Child | Additional Person Info | AllPersonExtraInfo | Y | Used for accessing personEFF which is valid on a given effective date | Read Person Additional Info Business Object |