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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Username Not Generated as per User Name Generation Rule
Summary:
Updating the User Name Generation Rule to Person or party number is not generating the username as required
Content (required):
- Till now we used User Name Generation Rule as FirstName.LastName (on TEST environment).
- For Production, client has requested to use the Person Number as the Username. So, we have updated the User Name Generation Rule from FirstName.LastName to Person or party number in the User Category Information from Security Console on TEST environment to check and confirm the scenario.
- After performing the above steps, I converted the Pending Worker to an Employee (which follows the Hire an Employee approval process flow) after bypassing the approvals.
1