Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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 with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Restrict field update based on Action reason selected on transactions like Request a Position Change

edited Sep 11, 2023 2:15PM in Human Capital Management 4 comments

Summary:

Restrict field updates based on Action reason selected on transactions done through responsive pages

e.g. Request a Position Change - when the action reason is selected as Change in Location. the user should only update the location attribute,

Content (required):

below are some options we have explored,

our first stab is on Request a Position change transaction, restrict field updates based on action reason selected in the When and Why section.

if action reason is selected as Change in Location.

the user should only update the location attribute,

user should not be allowed to update any other attributes.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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