25C - Frequently Asked Questions

1. Frequently Asked Questions

2. Understanding Messages in Personalization Report

1. Frequently Asked Questions

Following section includes some of the frequently asked questions when using the HCM Redwood Helper Tool to analyze and migrate personalizations,
and provides detailed answers for each. If you have further questions, post them in Cloud Customer Connect forum.

Category Question Answer

1 Tool - new I don't want to install EXE or DMG, can I Yes, You can download Jar file. double clicking on JAR will open UI mode.
still use the Tool in UI mode?

2 Tool How does the tool work?

1. The tool works on the premise that each Responsive UI page/flow has a corresponding
Redwood UI page/flow
2. For each such page, tool internally uses a mapping file that includes mapping of the seeded
fields, flexfields, regions from the Responsive UI to its Redwood UI equivalent
3. The tool reads existing Responsive UI personalizations done using TDS and Page Composer
(from the ADF personalization file), and uses the mapping information to
a. Create a report with list of all existing personalizations for each selected module
b. Generate corresponding Redwood personalizations as a VB studio workspace

3 Tool What is the best practice for using the Responsive and Redwood flows are implemented using fundamentally different frameworks, with each
tool to analyze and migrate ADF one having their own personalization tools.
personalizations? Should I migrate one
page at a time or all at once? 1. Responsive - Page Composer, TDS
2. Redwood - VB Studio

The page implementations, the underlying UI components, and how personalizations work, are
fundamentally different between the two frameworks. The helper tool attempts to bridge the two
frameworks and migrates all supported ADF personalizations created using Page Composer and TDS,
and writes them as business rules that will work with VB Studio. The tool provides a report of what's
migrated and what's not. You should still manually verify the business rules created by the tool to
make sure they meet your business requirements. If additional Redwood personalizations are required
to meet the business requirements, you will use VB Studio to manually create business rules on top of
what the tool has created. If required, you can also edit the business rules migrated by the tool.

It is not recommended to migrate personalizations for all pages in one go. It will be very hard to
manage the validations of those migrated business rules. Recommendation is to migrate one product
at a time, and within each product, you can group them by VB extensions that is explained in the User
Guide.

4 Tool What can we expect in new versions of

the tool for each quarterly update? 1. If you download the ADF personalization file from a given env, run the 24C version of the tool
and 24D version of the tool against the same file, both versions of the tool will show in the report
the same set of fields that were personalized.
2. The new version of the tool may include any additional mappings of fields from Responsive UI to
Redwood UI. For example, if Redwood UI had enhancements to address any functional gap,
then appropriate Responsive UI Redwood UI field mappings may be introduced in the new
version.
3. The new version of the tool may also include enhancements to the report format, with additional
information for Customers to analyze existing personalizations better.

5 Tool Can the tool be used to migrate The tool is designed to be an one-time helper tool to help migrate all personalizations from
personalizations for a given module Responsive UI to Redwood UI. By one-time it means for example,
multiple times?
1. You are implementing personalizations for Redwood UI "Personal Details" page
2. To migrate existing personalizations from Responsive UI to Redwood UI, you
a. Run the tool for module "Personal Details" by passing ADF personalization file downloaded
from prod
b. Review the report of all existing personalizations in Responsive UI
c. Use the generated VB workspace and import to VB studio in your dev env where you are
testing Redwood UI
d. Manually implement additional personalizations in VB studio to meet additional
personalization requirements
e. Test and publish the personalizations for "Personal Details" in your dev env
3. While Redwood "Personal Details" personalizations are being tested in your dev env, and not yet
deployed in production, you have made new personalizations to Responsive "Personal Details"
page in prod based on some new user requirements. In this case, you have to implement the
new personalizations (delta from the originally migrated personalizations from Step 2 above)
manually to corresponding Redwood "Personal Details" page as well, you can not use the tool to
migrate only the delta.
a. The tool is not designed to identify only the delta from the previous run of the tool.
b. The tool always migrates all personalizations in the given ADF personalization file.
6 Tool Can I use the tool to migrate No. The tool is not designed to migrate personalizations from one HCM environment to another. This
personalizations from one HCM tool should be used against one single HCM environment where you are implementing Redwood
environment to another? personalizations. You download ADF personalizations from the HCM environment, migrate them using
the tool to Redwood, and import them to the same HCM environment, and complete your testing.

Once all required Redwood personalizations are implemented on the given HCM environment, you
can migrate them to other environments using appropriate VB Studio tools to migrate them. Refer to do
cumentation.

7 Tool Does the tool process Autocomplete No. The tool only processes UI personalizations done to Responsive UI pages using Transaction
rules, such as validation and defaulting Design Studio and Page Composer.
rules created on certain business objects?

8 Tool What happens when I DO NOT provide a When you select Mode as Migrate and Report, and do not provide a VBS workspace, following
value for parameter VBS Workspace happens.
when running the tool?
1. The tool shows all the modules grouped by product and VB extension the page belongs to
2. You can select any number of modules across any groups
3. When you run the tool, the personalizations are migrated and written as business rules to VBS
workspace each workspace named with the VB extension. For example, if you select one or
more modules under group Global Human Resources - Oracle Hcm Employment Common
Processes Extension, the migrated business are written to VBS workspace named VBSWorksp
ace-oracle_hcm_employmentprocessUI-updated.zip
4. To import this to VB Studio, create a workspace with one of the pages from this group, and
import the generated VBS Workspace

9 Tool What happens when I provide a value for If you want to migrate personalizations into an existing VBS Workspace,
parameter VBS Workspace when running
the tool? 1. Go to VB Studio and create a workspace with one or more pages that you would like to work on
2. Go to Advanced Mode and export the workspace. This workspace now has configurations
initialized corresponding to the pages you had added to it.
3. When you provide this exported workspace as input to the tool, the tool only shows modules that
belong to the VB extensions that are initialized in the workspace.
4. You can select one or more modules from the list, and migrate the personalizations.
5. The migrated personalizations are written to the provided VBS workspace, named <Original
VBS workspace filename>-updated.zip.
6. You can now go to VB Studio, and import the updated VBS workspace with the migrated
business rules.

10 Tool What should I used as the HCM The HCM Environment URL should be of the below format that you can copy after signing in to your
Environment URL in the tool? HCM environment, after Home page loads.

https://fa-xxxx-test-saasfaprod1.fa.ocs.oraclecloud.com

DO NOT use,

1. Any part of the URL after ".com" such as "/hcmUI/faces/FuseWelcome"

2. Login URL like https://login-xxxx-test-saasfaprod1.fa.ocs.oraclecloud.com/

11 Tool Can I use the tool in Production? No. You should not use the tool directly in Production to migrate personalizations. This tool is
expected to be used only during your personalization development phase.

You will use a Stage environment where all your personalizations will be developed, and tested for
user acceptance. Once all personalizations are completed, and tested in the Stage environment, you
will use appropriate migration processes provided by VB Studio to move the personalizations from
Stage to Production.

12 Tool I already have an older version of the tool If you already have and older version of the tool installed in your computer, uninstall it and reinstall the
installed. How do I upgrade to the new new version of the tool.
version of the tool?
After reinstalling the new version of the tool, remember to check the Settings to make sure

1. Proxy host and port are set, if not set again

2. Re-import the custom CA certificates again if you had earlier imported them in the older version
of the tool

13 Tool Can I use the older version of the tool It is strongly recommended to use versions of the tool that correspond to your HCM environment.
against a new version of the HCM
environment? For example, 24B version 1. 24B version of the tool against 24B HCM environment
of the tool against 24C HCM environment. 2. 24C version of the tool against 24C HCM environment

14 Tool How does the tool identify the The tool uses metadata corresponding to each module to migrate relevant ADF personalizations. The
personalizations from Design Studio and metadata essentially provides mappings of attributes from the Responsive pages to corresponding
Page Composer and map it to Redwood pages. The mapping metadata corresponding to the modules are packaged with the tool.
appropriate VBS fields?

15 Tool I exported the migration set from You can use the downloaded configuration file as is. You are not required to further extract the
Configuration Migration. Can I use the contents of the downloaded file. The tool automatically extracts the required ADF personalization file
downloaded JAR file as is, or should I from the downloaded file.
extract another file from downloaded file?
16 Tool There are some modules that only print a Those modules that are listed in table 6.2 produce only reports. These modules either do not have
HTML report with only IDs of the Redwood pages implemented, or Redwood pages are implemented but are not supported for
personalized attributes. There are no personalization in VB Studio. These modules only print report.
details for the attributes, and the
personalizations appear as not migrated.

17 Tool Do I have to reimport the custom CA Yes. If you uninstalled an older version of the tool, and installed new version of the tool, you have to re-
certificates and/or set Proxy Host and import the custom CA certificates again because the new version includes a fresh copy of the
Port after reinstalling a new version of the certificate trust store.
tool?
While the proxy settings are persisted, and will be reused even after a new version is installed, make
sure to go to Settings and verify before using the tool.

18 VB Studio In VB Studio, I created Workspace1, This is expected. If you exported VBS Workspace1, after migration always import it back to the same
exported it and used it to migrate workspace in VB studio.
personalizations to. Now, I imported it to
another VBS workspace Workspace2.
This overwrites the existing unpublished
rules in Workspace2.

19 VB Studio In VB Studio, I created a workspace, You have two options to revert to original stage, and discard migrated business rules.
added some custom business rules
manually, exported it, and used the 1. Manually delete all the migrated business rules and any guided journey personalizations. All
exported workspace to migrate migrated business rules either start with TDS_ or PageComposer_.
personalizations from ADF. Now the 2. Reimport the original exported workspace that only included your custom rules.
updated workspace contains my custom
rules, and migrated rules.

I imported this updated workspace to VB

Studio and tested. I want to discard only
the migrated personalizations.

20 VB Studio In TDS, the flow supported certain rule Not all rule conditions supported in TDS may be available in VB Studio for the Redwood page. If you
conditions such as "Country", "Role" but see a message in the Report that certain rule condition is not supported in Business rules, you can
the helper tool report shows below error. double check if that rule condition is supported in VB Studio for that specific Redwood page.

Rule condition "rule condition field" used Go to the Redwood page, and click Edit in Visual Builder Studio. Create a business rule manually and
to personalize the Responsive page is not check if you are able to use Role or an appropriate attribute in the rule condition. If you are not
supported as rule condition in Business allowed to create the rule manually in VB Studio with that attribute, then it means the support is not yet
Rules. available.

For further clarifications, you may post in Cloud Customer Connect forum.

21 VB Studio When I select my VBS workspace in the To make sure the VB extensions are initialized correctly in the workspace, before exporting the
tool, it shows message "Selected workspace from VB studio, go to Configure Fields and Regions for each page and create a dummy
workspace doesn't have any VB rule under Form Rules. Now export the workspace and use it in the tool.
extensions. In VB Studio, add required
Redwood pages to the workspace before You can later delete the dummy rules after re-importing the updated workspace to VB Studio.
exporting it for use with the tool".

22 Design If the Design Studio rules include The rule conditions actually use the IDs for comparison during runtime, and the display names are
Studio conditions that check for a Legal only for user readability.
Employer, Business Unit etc, the
migrated VBS Business Rule only shows The display name for these IDs are not available during migration, but after importing the migrated
the ID value instead of display name. For VBS workspace to VB Studio, you may edit the rule so the display name is populated.
example,

[[ $componentContext.Grade === 29 &&

$componentContext.BusinessUnit ===
100000016898794 ]]

23 Design I have inactive rules in Design Studio, All Design Studio rules are migrated, both active and inactive. The active Design Studio rules are
Studio and they are also migrated to VBS migrated as active Business Rules, and inactive as inactive. These migrated rules can then be used or
business rules. discarded as required.

24 Design In Design Studio, an attribute is present in While the Page Attributes personalization has precedence when the application is accessed, the
Studio both Page Attributes and Available migration tool migrates the personalization that was performed last. You should review the migrated
Attributes. I have personalized the personalization, and make sure your requirements are met by the migrated rules.
attribute under both sections, which one
will be migrated?
25 Design Is there a list of modules for which "Show "Show Questionnaire" for following modules are supported.
Studio Questionnaire" personalization is
processed? 1. Add Pending Worker (add-pending-worker)
2. Change Assignment (assignment-page)
3. Create Work Relationship (create-work-relationship)
4. Employment Add Assignment (employment-add-assignment)
5. Employment Contracts (employment-contracts)
6. Employment Start Dates (employment-start-date)
7. Change Location (location-page)
8. Change Manager (manager-page)
9. Terminate Employment (terminate-employment-page)
10. Transfer (transfer)
11. View Employment Details (view-employment-details)
12. Recruiting Job Referral (recruiting-job-referral)
13. Create Pool (create-pool)
14. Change Working Hours (workinghours-page)

26 Design In TDS, only one field was personalized. Some attributes when personalized in TDS, for example an Select One Choice field is marked as
Studio But in the report generated by the tool, "Required", internally the system updates the personalization to multiple component ids.
the same field is repeated more than
once with same display name and When the tool processes the ADF personalizations, it displays the personalization for each internal
personalization but different IDs. component ID, although it's eventually only one UI attribute.

27 Design In TDS, I have created a rule that This sample TDS rule includes two rule condition attributes, (1) Country, and (2) Business Unit. In the
Studio includes multiple conditions such as, corresponding Redwood page, it is possible that one or both of the rule condition attributes are not
available to be used in the business rule. For example, if the page does not support using Business
1. Country = "US" and Unit in business rules, then the tool does not migrate the rule completely.
2. Business Unit = "US BU"
To verify further, bo to VB studio for the Redwood page and check if you can manually create a
The tool processed the rule and printed in business rule using the rule condition attributes. If the VB studio doesn't allow creating business rules
the report that the rule is not migrated. using the specific rule condition attributes, then it is expected that the tool marks the rule as not
What could be the reason? migrated.

For further questions about when certain features would be available, post a question to the
appropriate product forum in Cloud Customer Connect.

28 Design In TDS, I have created a rule that The tool first evaluates the rule condition attributes used in the TDS rule, such as Role, Legal
Studio includes several different personalizations Employer, Country, Business Unit, etc to make sure they are also supported in the corresponding
for various attributes and regions. After Redwood page to be used when creating business rules. If all rule condition attributes are supported,
running the tool, I observe that for the it checks the personalized attributes and regions.
same rule, some personalizations are
listed under "Personalizations that are 1. If all the attributes and regions are mapped and available in Redwood page, then they are fully
migrated" and some are listed under migrated and listed under "Personalizations that are migrated"
"Personalizations that are not migrated". 2. If some attributes and regions are mapped and available in Redwood page, then those are
What could be the reason? migrated, and rest are not migrated and listed under "Personalizations that are not migrated".

29 Page Using Page Composer, I have added Custom content such as text, and link should be implemented in Redwood pages using Guided
Composer custom content to my Responsive pages Journeys. Such custom content embedded using Page Composer cannot be migrated.
such as static text as instructions for the
users, a link to our company policies, a Refer to Guided Journey documentation for more details on how to show custom content in Redwood
link to a custom BI report etc. Are they pages.
processed by the helper tool and
migrated to Redwood page?

30 Page In Page Composer, I have various Page Composer is not a rule based personalization tool similar to TDS or Business Rules. The tool
Composer personalizations that use complex EL only migrates Page Composer personalizations that use a simple EL expression such as #
expressions. Will they be migrated? {securityContext.userInRole['role']}.

All others are not migrated, and will be printed in the report indicating the same. These will have to be
reviewed and implemented manually.

31 Page Using Page Composer, I have In Page Composer, "showRequired" and "Required" are two different properties with different usage.
Composer personalized showRequired property for
an attribute, but it is not migrated. 1. showRequired - There is no corresponding personalization property in VB Studio
2. Required - This is migrated to VB Studio successfully

Responsive UI personalizations such as ShowRequired, AddRendered can be safely ignored since

they are not relevant in Redwood pages.

32 Page In Page Composer, I have personalized

Composer properties such as disabled, editable, and 1. disabled is mapped to readOnly, for example, disabled=true is equivalent to readOnly=true
rendered. How are these mapped to VBS 2. editable is mapped to readOnly, for example, editable=false is equivalent to readOnly=true
personalizations? 3. rendered is mapped to hidden, for example, rendered=false is equivalent to hidden=true

33 Page Using Page Composer, I have Yes. Redwood is a complete reimplementation of the HCM UI flows using a different framework. Not
Composer personalized elements that are not fields all components and layout used in the Responsive pages may be available in their corresponding
or regions in the page, they are elements Redwood pages. Since such components may not be available in the new Redwood pages, such
such as Button, Group Layout, List View, personalizations may not be migrated. VB Studio only allows to personalized regions and fields.
Panel Header, Select One Choice, and so
on. That are not getting migrated. Is it
expected?
34 Common We have updated flexfields using Manage No. Flexfield definitions that you updated from Manage Description Flexfields are not required to be
Descriptive Flexfields task to add global migrated. Both Responsive and Redwood flows refer to the same flexfield definitions from your HCM
and context segments. Do they require to environment.
be migrated as well as part of Redwood
uptake? Only if you personalized the flexfields and their segments in the application UI using TDS or Page
Composer, they will require to be migrated.

35 Report The helper tool generated report that It is important to note that ADF pages were personalized as below
included several attributes without the
display name. We are unable to 1. Using Page Composer to modify a variety of properties of attributes and regions by looking at the
recognize those attributes. page structure
2. Using TDS to personalize only a given functional flow by selecting specific set of properties for
attributes and regions without ability to modify the underlying page structure

There may be personalizations done using Page Composer to various component ids that are not
relevant in Redwood flows. For example, moving a region, rearranging fields etc. The tool doesn't
recognize such personalizations, and hence it writes them as is in the report under "Not migrated"
section.

When reviewing the report and migrated personalizations, it is important to review the ones that were
migrated successfully, and verify them to make sure the business requirements are met. To implement
additional requirements, use VB studio to manually create business rules.

36 Common After importing the VB studio workspace This banner is shown if your current workspace to which you are importing the new workspace does
created by the tool, I see yellow bar not include the required dependencies.
saying, "Upgrade your application"
To resolve this, you need to follow below steps:

1. Navigate to Git tab in Visual Builder Studio home page

2. For each project like oracle_hcm_employmentprocessUI, oracle_hcm_gradesUI etc, create one
dummy rule for any one layout.json
3. you can verify dependencies in extension.json after above step
4. banner will go away.

37 Common After importing workspace and previewing preview will show blank page when dependencies are not properly created for your working
changes, i do see blank page workspace.

To resolve this, you need to follow below steps:

1. navigate to Git tab in visual studio

2. for each project like oracle_hcm_employmentprocessUI, oracle_hcm_gradesUI etc, create one
dummy rule for any one layout.json
3. you can verify dependencies in extension.json after above step
4. preview changes again

38 Common I have generated report from tool but for You can create a Post in Customer connect forum for this clarification
few attributes, Display names are not
shown in report

39 Family and I have many customizations done for family and emergency ADF module is divided into 5 different VBCS modules.
Emergency Family and Emergency Contacts UI. but
Contacts running tool for family and emergency 1. Family and Emergency Contacts
contact module is showing few 2. Create Coworker as a Contact
customisations only. 3. Change Contact Start Date
4. Create New Contact
5. Edit Contact

VBCS Family and Emergency Contacts is for listing page of contacts. if ADF customisation is not
applicable for VBCS Family and Emergency Contacts then it will be skipped.

2. Understanding Messages in Personalization Report

For personalizations that are not migrated or not migratable, the report includes a message in Comments column that explains the reason why it was not
migratable. Following are some common messages, and description for each of the messages. If you have further questions, post them in Cloud Customer
Connect forum.

Message Description

1 Attribute "AttributeName" is either not available in Go to the Redwood page and confirm if the attribute is available. If available, go to VB
the Redwood page, or it is available but cannot be studio and check if that attribute is available for personalization using Business Rules. If
personalized in Business Rules. Go to VB Studio for available for personalization, you may personalize it manually as per your business
this page and confirm if the corresponding field is requirements in VB Studio.
present, and you are able to personalize it.
If you are unable to identify the attribute, post in Customer Connect forum for review.

2 Attribute "AttributeName" is not available in the The attribute that was personalized in Responsive pages may not be relevant in Redwood
Redwood page. You may safely ignore this page any more. Such personalizations can be safely ignored.
personalization since it is not relevant in the
Redwood page.
3 Attribute "AttributeName" is available in the The attribute that was personalized in Responsive pages may not be personalizable in
Redwood page, but cannot be personalized in Redwood page as per product design. If the report from the tool indicates the attribute
Business Rules. Go to VB Studio for this page and cannot be personalized, you may try to personalize the attribute manually in VB Studio.
confirm if you are able to personalize the field.
If you are able to personalize the same attribute manually, then you may post this as an
issue in Cloud Customer Connect forum.

4 Attribute "AttributeName" is available in the Go to VB studio for the Redwood page and check if that attribute is available for
Redwood page but not available for personalization personalization using Business Rules. If it is not available for personalization, then this
in the Business Rules hence it is not processed. message is expected.

5 Attribute "AttributeName" is available in the The attribute is available in Redwood page, and is available in VB Studio for
Redwood page but its property "PropertyName" personalization, but a certain property such as "Required" or "Read Only" may not be
cannot be personalized using Business Rules. available for personalization. The property may be prevented from personalization as per
product design.

Go to VB studio for the Redwood page and check if the property for that attribute is
available for personalization using Business Rules. If the property is not available for
personalization, then this message is expected.

6 Rule condition "RuleCondition" used to personalize The rule condition has various rule condition fields such as Role, Country, Legal
the Responsive page is not supported as rule Employer, etc., If the Redwood page does not yet support all the rule condition fields, then
condition in Business Rules. Review the business the Responsive personalization may not be migrated to Redwood. In such cases, review
requirement, and manually implement this your business requirement, investigate the options available in VB Studio and implement
personalization appropriately in business rules. the personalization manually.

7 Personalization to be migrated as constant but the In Redwood page, personalizations can be done only using constants, they cannot be
personalization present in Responsive page is configured using Business Rules to be used conditionally. For this reason, only those
configured using rule conditions. personalizations in Responsive page that were configured using Global rule (to be used
always), are migrated to page constants in VB studio.

8 Descriptive Flexfield "Flexfield" is not processed The tool uses REST APIs to load flexfield related metadata from your HCM environment
because the flexfield may not be configured in the to process them from the ADF personalization file. If the flexfield doesn't have any
HCM environment you are connecting to. segments created, the REST API may not load any metadata, and hence their
personalizations in Responsive page may not be processed.

9 Descriptive Flexfield "Flexfield" is not processed Before clicking Submit in the tool, click "Include Flexfields"
because "Include Flexfields" parameter was not
checked while running the tool.

10 Existing personalization in this Responsive page Responsive pages may have been personalized using Page Composer and Design
uses an EL expression that may not be Studio. While Design Studio is rule based functional personalization of flows, Page
automatically converted to business rule conditions Composer provided ability to create personalizations on individual page components such
in VB Studio. Review the business requirement, and as fields, regions, etc using EL expressions to control the behavior. Not all EL expressions
manually implement this personalization that were possible in Page Composer can be converted automatically to a rule condition in
appropriately in business rules. VB Studio.

In such cases, review the EL expression used in Page Composer, and you may
personalize manually as per your business requirements in VB Studio.

11 Personalizations to show custom link, custom text, In Responsive pages, you may have used Page Composer to insert custom content such
BI report etc., in Redwood page are supported only as a link to a page, link to a custom BI report, custom text providing instructions to users
using Guided Journeys. Refer to Guided Journey etc. In Redwood page, the same is achieved using Guided Journeys.
documentation for more details on how to show
custom content in Redwood pages.

12 Existing personalization in this Responsive page Page Composer personalizations such as "move" used to rearrange components on the
uses a custom element. Such personalizations are page are not supported in VBS Business Rules, and hence the personalization is not
not supported in Redwood pages. processed.