Project handling - advanced

During creation, progress, completion and cancellation, there are several ways the projects are handled if you specify various advanced options.

Project Title Prefix

Where certain properties are defined on a site page, the project name is automatically prefixed on the second page of the project creation wizard. The configuration is set in /system/console/configMgr and supports properties called Brands, Business areas and Divisions.AEM Title Prefix

Custom parameters during project creation

If a project option to support additional attributes is configured and enabled, the attributes are displayed in the project creation wizard (step 2). The supported attributes are Input (limited to 50 characters), picklist and selection.

Preselect the cloud configuration based on page properties

Where cloud configuration properties are defined on a site page, the cloud configuration is pre-selected on the second page of the project creation wizard. The feature saves time and ensures that the correct cloud configuration is set.

If the page chosen does not have a cloud configuration setting in the page properties, there are 2 solutions the AEM Cloud connector implements:
  • The AEM Cloud connector looks up the page hierarchy until it finds a cloud configuration property on a parent page.
  • If the connector reaches \content without finding a cloud configuration, the default cloud configuration is selected.

During the project creation wizard, you can see a link icon next to the Cloud Config field showing that the cloud configuration has been inherited.

Preselect target languages based on the configuration page property

The system can be instructed to auto-select all the target languages that the cloud configuration supports.

Preselect target languages based on the previous selection

The system can be instructed to remember the source and target languages set in the previous project created by a user. This feature saves time, especially if a given user creates projects based on the same language sets.

Launch path in AEM jcr

AEM developers can use the launch path of the AEM translation project to trigger automated processes post-translation, such as the auto-publishing of content to the website. AEM Translation Framework creates different launch paths depending on how the project is created such as a default language copy, live copy or launch.

To enable this feature, RWS includes a jcr node called sdl_sourcePath in the translation project with a consistent path to the translation page.

Launch path