Form Personalization: Benefit Group Field Cannot be Made Mandatory for Contact (Doc ID 1908936.1)

Last updated on AUGUST 10, 2017

Applies to:

Oracle Human Resources - Version 12.1 HRMS RUP5 and later
Information in this document applies to any platform.

Symptoms


Form personalizations implemented to get "Benefit Group" field mandatory, ie yellow and with no way to save any record if no value in "Benefit Group". It's working fine for contact created thru the people form.
It's NOT working for contact created thru the Contact form first.

 

Steps to Reproduce:
The issue can be reproduced at will with the following steps:


1. Implement form personalization to get the Benefit Group Mandatory.
2. Create the contact: HRMS Manager > People > Enter and Maintain > Retrieve an employee > Others > Contact > Create a contact (Type: Candidate, relationship: brother) > Save
3. Retrieve the contact: HRMS Manager > People > Enter and Maintain > Retrieve the contact just created > Benefit Group tab: See the Yellow field
4. Update the contact but leave the Benefit Group field blank.
5. It's possible.

 

FORM PERSONALIZATIONS

 

Help > Diagnostic > Custom Code > Personalize

 a) Level: Function


 Condition :-
 Trigger Event: WHEN-NEW-BLOCK-INSTANCE
 Trigger Object: PERSON
 Condition: blank
 Processing Mode: Not in Enter-Query Mode
 Action:-
 Seq: 1
 Type: Property
 Object Type: Item
 Target Object: PERSON.D_BENEFIT_GROUP_NAME
 Property Name: REQUIRED
 Value: TRUE


 b) Level: Function


 Condition :-
 Trigger Event: WHEN-NEW-BLOCK-INSTANCE
 Trigger Object: PERSON
 Condition: :PERSON.D_BENEFIT_GROUP_NAME IS NULL
 Action:-
 Seq: 2
 Type: Property
 Object Type: Item
 Target Object: :PERSON.D_BENEFIT_GROUP_NAME
 Property Name: ITEM_IS_VALID
 value: False




Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms