You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started: AI Resources for Oracle Cloud HCM – Go Here

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

Name Change Approval

in Human Capital Management 1 comment

Summary:

We currently have the following name change rule built out but it looks like all personal and demographic changes are routing for approval because of this rule. I am not sure what in this rule is causing the all personal and demographic changes to route for approval.

((Current Person GlobalName.result.MiddleNames != "Task.payload.Proposed Person GlobalName.result.MiddleNames") OR ((Current Person GlobalName.result.LastName != "Task.payload.Proposed Person GlobalName.result.LastName") OR (Current Person GlobalName.result.FirstName != "Task.payload.Proposed Person Contact GlobalName.result.FirstName")))

Content (please ensure you mask any confidential information):


Version (include the version you are using, if applicable):

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!