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.
Personal Details are not migrated using the Personalization Tool 24D.
Summary:
We used the Personalization tool to migrate all the Core HR changes from Responsive to Redwood into one of the pods.
In this process we selected all the corresponding GHR extensions available in the tool. We did not pick the pages/module names viz:identification-info, personal-details etc explicitly, but selected the parent extension like - Oracle HCM People Personal Information Extension.
When we start testing we could see that, the "Persoanl Details" page personalizations are not pulled but "Additional Personal Info" page changes are pulled as a TDS... rule. The report generated from "Migrate and Report" though shows the "Personal Details" rule migrated as "TDS_Personal..... ".
Tagged:
0