Step by step guide on how we can transition from Responsive pages to Redwood pages in Oracle Fusion Cloud HCM
Hello Curious Minds!
This document outlines the steps, process
and reference on how HCM Fusion Cloud Customers can smoothly transition from
Responsive UI to Redwood Pages.
We will try to cover all aspects that needs
to be considered for this transition.
Redwood is a new user experience in Oracle
HCM Applications. Many pages and flows have been recreated in the Redwood
toolset Visual Builder Studio (VBS) to improve the user experience by having
the pages and flows be more connected.
Fortunately, moving to Redwood offers many
benefits including GenAI, and it doesn’t have to be hard.
Step by step Approach
1.
Environment: first and foremost, we need to setup a test environment. Here we can
have two test environment one publishable where we can set the profile options
to redwood and other environment in responsive UI. Having two test environments
will help us in comparing if everything is working as expected.
Prerequisites
· Oracle Search must be enabled for redwood for HCM
Customers using custom
roles must stay current with the new security privileges
Helpful Links
Expected Outcome
·
The test environment is
identified, and prerequisite steps are run in the environment
·
Vision Builder Studio is
provisioned and ready to use
·
Remember to enable the redwood
baseline Administrator Profile Value: ORA_HCM_VBCS_PWA_ENABLED
2.
Identify the pages to be
moved: we need to list out all the set of pages
that need to be converted into Redwood. We can refer the below document to see
which of the pages have redwood features and what will be the profile options
that need to be enabled
We can have different approaches
to move to Redwood
By Audience (Employee then
Manager)
By HR Business Process
Calendar (Goals in Feb then performance document in September)
By module / data type
(Core HR Person information then payroll information)
By Complexity of
personalization (Low complexity first then medium then high)
By Potential of business
impact (Highest time consumption tasks or frequency of transaction list)
3.
Assess impacts: We need to carefully identify how adaption to redwood will impact
security, features, personalization’s and business rules. We can also compare
and check between two test environments for each transaction how the flow
works. Will all the features be available, will the end result of the
transaction remain same, which of the flex fields are missing. We can use the
Oracle provided tool to analyze existing personalization’s to Responsive flows and migrate them to their corresponding Redwood User Experience. Below document
will help us in understanding the tool
-This tool reports on your responsive UX page personalization’s made
with page composer or Transaction design studio
-Indicates which personalization’s are supported in your current
version of Visual Builder Express Business Rules
-Offers the option to
migrate supported personalization’s to your redwood environment, specifically a
VBS workspace
-A new version of the tool
will be released every quarter to support the latest HCM updates
Document
2999756.1
We can segregate impact
assessment across the following areas
|
Assessment Area |
Assessment Approach |
|
Security |
Review Oracle release notes to identify any impact |
|
Feature Parity |
Compare the RUI and Redwood pages |
|
Experience Design Studio personalization |
Use Oracle Personalization helper tool |
|
Page Composer Personalization |
Use Oracle Personalization helper tool |
|
Auto Complete Rules |
Autocomplete default rules need to be migrated manually;
autocomplete validation rules should work as is |
|
New Functionality |
Review oracle release notes for additional information |
T-Shirt Sizing Guidelines
|
Level of Impact |
T-Shirt Size |
|
No Impact |
XS |
|
No Personalization but some new features |
S |
|
Personalization but no auto-complete |
M |
|
Personalization’s with auto complete validation rule only |
L |
|
Personalization’s with auto complete validation/Default rule |
XL |
4.
Review with Business
Owners: Once we have listed out all the features
and pages it's time to come together with business and decide what’s best for
the organization, which features alone needs to be enabled.
5.
Finalize the plan: As we set the list with pages that needs to be converted into Redwood,
we have to create build and test plans, write test scripts. Identify key
resource person’s that will be involved in each phase of the development, set
the dates for each phase, discuss with stakeholders on their availability for
the final testing
-Review upcoming patches and quarterly release dates
-modify help documents
-Review quarterly release plan to identify any impact to existing
pages
-Review the known redwood consideration list to account for any
delays
6.
Build Test and Deploy: Once we get signoff on the plan, we start with analysis then build
test and deploy. During this period, we can reach out to oracle via oracle
support on any issues related to transition.
you will find curated details for each module individually
Comments
Post a Comment