If you're using the HCM Personalization Helper tool in report only mode, a Visual
Builder Studio workspace isn't required. However, if you're using the tool to migrate
personalizations, a Visual Builder Studio workspace is required.
Prepare the workspace
-
Go to the Redwood page that you want to personalize, such as Hire an
Employee.
-
Click .
-
Select a project from the list or create a new one. Visual Builder Studio opens
the page in Express Mode by default.
-
In the Business Rules section of the page, click Configure Fields
and Regions and create a test business rule. This initializes
required dependencies for this page in the Visual Builder Studio
workspace.
The workspace now has Employment Core Visual Builder extension initialized so
you can use this workspace to migrate personalizations for any page within the
extension.
-
To migrate personalizations from other Visual Builder page extensions, do the
following:
-
Search for the page (for example, Personal Details) and open it.
-
Click Configure Fields and Regions and create a
test business rule. This initializes required dependencies for this page
in the Visual Builder workspace.
The workspace now has Person Information Visual Builder extension
initialized. You can now use this workspace to migrate personalizations for
any page within this extension.
Now the Visual Builder studio workspace is initialized with required Visual
Builder extensions so you can migrate personalizations for the Redwood pages
that belong to those extensions.
Export the workspace
-
Click Advanced to move into Visual Builder Studio
Advanced mode.
Note: HCM supports Visual Builder Studio Express mode to
personalize Redwood pages. Use Advanced mode only when importing or
exporting a workspace.
-
Click the Git icon on the navigator to open the Git menu.
-
To save the current changes in the workspace, click
Commit.
-
If you don't want to save the current changes to the workspace, click
Stash.
-
Click .
-
Copy the downloaded .zip file to the same working directory where the HCM
Redwood Personalization Helper .jar file is. You'll use this file as the Input
workspace.
Results:
The Visual Builder Studio extension details are included in the workspace and are
based on the Redwood page you exported. The HCM Personalization Helper tool uses the
extension information from the workspace to show the list of modules you can select
to migrate personalizations from. So, if you export a workspace with the Hire an
Employee page, then you'll see all the pages from the same Visual Builder extension.
For example, the Employment Common Processes extension will include the Change
Assignment and Promote pages.
If you need to migrate personalizations for pages belonging to more than one Visual
Builder extension, you must repeat steps 1 through 3 for at least one Redwood page
from each Visual Builder extension and add them to the same workspace. When using
the workspace with the HCM Personalization tool, you can select all the pages within
each Visual Builder extension.