1. How do I use the HCM Personalization Helper tool?
  2. Run the HCM Redwood Personalization Helper tool in Migrate and Report mode

11Run the HCM Redwood Personalization Helper tool in Migrate and Report mode

You'll use Migrate and Report mode to migrate existing responsive UI personalizations to a Visual Builder Studio workspace.

Before you start, be sure you're running the version of the HCM Personalization Helper tool that matches your Oracle Fusion HCM version.

Note: The HCM Personalization Helper tool lets you select only modules from the Visual Builder Studio extensions that you initialized to the workspace exported from Visual Builder Studio.
  1. Launch the Personalization Helper tool.
  2. Select your working directory.
  3. Select the Migrate and Report mode.
  4. Select the ADF Personalization File that you exported.
  5. Select the Visual Builder Studio Workspace if you exported one to your working directory.
  6. Search for and select the modules you want to convert. They're grouped by VB Studio extensions.
    Tip: To see a list of pages that are available for migration to the Redwood user experience and support business rules in Visual Builder Studio for personalizations, see Table 6.1 in HCM Redwood Personalization Helper Tool (MOS Document 2999756.1).
  7. If flexfields are used in your personalized pages, select Connect to HCM Env and enter the environment URL and user credentials.

    The tool uses a REST API to retrieve flexfield metadata.

  8. Submit the process.

You'll find an output folder in the working directory with these files:

  • Visual Builder Studio workspace: Includes converted personalizations to import into Visual Builder Studio. If you exported an existing workspace, the file will be called <original name of the VBS workspace>-updated.zip.
  • HTML output file: Lists the modules selected for processing, along with the related personalizations from Transaction Design Studio and Page Composer. See the HTML report results for more details.
  • XLSX output file: Lists all the modules (including personalization details) in the first two tabs. For each module, the tool creates a tab for Transaction Design Studio (TDS) and for Page Composer personalizations.