Get Started: AI Resources for Oracle Cloud HCM – Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Note!! Please register for a free account to access the full content and also to participate in Q&A in the community
Action on personalizations that can’t be migrated
Hello Team,
I have executed the redwood personalization tool for my configurations, and identified some of the personalizations can’t be migrated.
May I know what we need to do on personalizations that cannot be personalized using Business Rules. Do we need to create the complete page using VBCS with all our personalizations? Kindly advise.
Example:
My use case is India employees should not have edit option to change their Name’s. This we have customized using Page composer in responsive UI. Now this can’t be done in Redwood? Need your suggestion on this.
Page Composer Personalizations | ||||||
|---|---|---|---|---|---|---|
File | Field | |||||
0