Skip to main content

Translating Page Designer Content (Legacy Manual Process)

Salesforce Commerce Cloud does not have an API that supports the translation of Page Designer content via the Connector. However, these pages can be manually exported, translated, and imported back into Commerce Cloud.

The following steps guide you through a work-around to translating Page Designer content.

This article describes the legacy manual process. For the latest automated process, see Translating Page Designer Content.

Step One: In Salesforce, Create an Export Job

  1. In your Salesforce instance, go to Administration > Operations > Jobs

  2. Click New Job

  3. Enter an ID (required) and a description (optional)

  4. Click Create
    ​

    Screenshot_2023-01-05_at_16.38.30.png

  5. Next, click the Job Steps tab

  6. Select the flow where you want to add a step

  7. Click Configure a step, and select a step
    ​

    Screenshot_2023-01-05_at_16.42.56.png

  8. Configure the step parameters:

    1. ID: a required unique ID for the job step identifier

    2. ExportFile: export file name and path relative to 'IMPEX/src'. All path folders must exist.

    3. OverwriteExportFile: select this checkbox

    4. PageIDs: a JSON object containing the single property 'page_ids', which is an array of Page IDs, e.g.: {"page_ids": ["campaign-example", "homepage-example"]}

    5. Locale: the Site source locale for which the Page data will be exported

      • This should match with the source locale of your Smartling SFCC Project

    6. FileFormat: the format in which the data will be exported, e.g.: JSON

  9. Click Assign
    ​

    Screenshot_2023-01-05_at_16.45.46.png

  10. Under Scope, add a scope for the flow by selecting specific sites

  11. Click Assign

Step Two: In Salesforce, Create an Import Job

  1. In your Salesforce instance, go to Administration > Operations > Jobs

  2. Click New Job

  3. Enter an ID and description

  4. Click Create

  5. Next, click the Job Steps tab

  6. Select the flow where you want to add a step

  7. Click Configure a step, and select a step

  8. Configure the step parameters:

    1. ID: a required unique ID for the job step identifier

    2. WorkingFolder: the folder that contains the import files, relative to the 'IMPEX/src/' folder

      • If not defined, 'IMPEX/src/' is used as a working folder. The folder IMPEX/src/instance configured in the job. It can be more specific, IMPEX/src/smartling-translation for example

    3. FileName: the file name for the file to be imported (relative to the 'WorkingFolder'), for example, imported-pages.zip

    4. NoFileFoundHandling: the step exit status that will be used when no matching files are found

      • Supported values: OK, ERROR, WARN, NO_FILES_FOUND

      • Default Value: NO_FILES_FOUND. The default value is used in this job configuration

    5. ImportFailedHandling: the step exit status that will be used when the import process fails

      • Supported values: ERROR, WARN

      • Default Value: WARN. The default value is used in this job configuration

    6. AfterImportFileHandling: controls what to do with the imported file after successful or failed import

      • The handling is not performed if there was a locking problem, or if ImportFailedHandling is ERROR and the file failed to validate

      • Supported values: Keep, Delete, Archive, Archive Zipped

      • Default value: Archive. The default value is used in this job configuration

    7. ArchiveFolder: the folder to store archived import files

      • Used when 'AfterImportFileHandling' is 'Archive' or 'Archive Zipped'

      • Folder location relative to 'IMPEX/' folder. If not defined, 'IMPEX/archive/' is used

      • Default Value: archive. The default value is used in this job configuration

    8. FileFormat: the format in which the data will be exported, e.g.: JSON

  9. Click Assign
    ​

    Screenshot_2023-01-05_at_17.37.51.png

  10. Under Scope, add a scope for the flow by selecting specific sites

  11. Click Assign
    ​

For more information about Salesforce job creation, read Salesforce documentation.

Step Three: Export and Translate Content

  1. Run the export job manually or configure a schedule

    • You can find information about every job launch in the Job history tab
      ​

      Screenshot_2023-01-09_at_13.31.07.png

  2. To download an archive of requested content of pages stored in the configured ExportFile property path, go to Administration -> Site Development -> Development Setup, on the Folder Browser tab. You should navigate to Impex -> src folder

    Screenshot_2023-01-09_at_14.36.13.png

Step Four: Prepare The File For Translation

Consult your Solutions Archect about the directives required for your particular source file.

Step Five: Upload Files To Smartling For Translation

  1. In Smartling, go to a Files project

    • If you don't already have a Files project-type set up, follow these steps to create a project

  2. Create a Job by Requesting Translation

  3. When the Job is complete, download the translated files

Step Six: Import Translated Content to Salesforce Commerce Cloud

  1. Prepare translated content:

    • The translated filename must be the same as the source, with the suffix ‘_<target_locale>’

    • Translated files must be compressed to the archive. For example, with command zip -r9 imported_pages.zip campaign-example_fr.json homepage-example_fr.json

    • The archive must be uploaded to the SFCC folder configured in the WorkingFolder property of the import job

  2. Run the import job manually or configure a schedule.

    • You can find information about every job launch in the Job history tab

    • Translations will be applied if the job finished successfully

Screenshot_2023-01-09_at_14.47.41.png
Related Articles
Did this answer your question?