Configure Workfront for Experience Manager enhanced connector

A user with administrator access in Adobe Experience Manager configures the enhanced connector after installing it. For instructions to install, see Install the connector.

Configure event subscriptions

Event subscriptions are used to notify AEM of events that take place in Adobe Workfront. There are three Workfront for Experience Manager enhanced connector features that need event subscriptions in order to work, these are:

• Automatic creation of project linked folders.
• Synchronization of changes in Workfront document custom form values to AEM asset metadata.
• Automatic publication of assets to Brand Portal upon project completion.

To use these features, enable event subscriptions.

• Edit Workfront Tools Cloud Services configuration you created in step 5 and select the Event Subscriptions tab.

• Select the Workfront Custom Integration you created in section 6.

• Click Enable Workfront Event Subscriptions.

  

Configure linked folders

To subscribe to the events, follow these steps:

1. Navigate to the Event Subscriptions tab in the cloud services.
2. Select the custom integration created in Workfront.
3. Click Enable Workfront Event Subscriptions.

Linked folder structure configuration

1. Go to the Project Linked Folders tab in the cloud services.
2. Linked folder parent path: Select a folder in the DAM where you wish to create the linked folders. If left empty, it will default to /content/dam. Make sure that the Workfront Tools metadata schema and Workfront Linked Folder folder metadata schema have been applied to the selected folder.
3. Linked folder structure: Enter comma-separated values. Each value should be DE:<some-project-custom-form-field>, Portfolio, Program, Year, Name, or some “Literal String Value” (this last one with quotation marks). It is currently set to Portfolio,Program,Year,DE:Project Type,Name.
4. Build linked folder title in Workfront using the folder structure names checkbox should be checked if the title of the folder in Workfront should include all folders in the structure. Otherwise, it will be the title of the last folder.
5. Sub-folders multifield lets you specify a list of folders that should be created as a child folder of the linked folder.
6. Project status: Select the status the project has to be set to in order to create the linked folder.
7. Create a linked folder in projects with portfolio: List of Portfolios that the project has to belong to in order to create the linked folder. Leave this list empty to create the linked folder for all project portfolio.
8. Create a linked folder in projects with custom form field: Custom form field and its corresponding value that the project has to have in order to create the linked folder. This configuration will be ignored if left empty. Select CUSTOM FORMS: Create DAM Linked Folder for the field and input Yes for the value.
9. Click on Enable automatic creation of linked folders. If you go back to the Event Subscriptions tab, you’ll see there is now one create event.

Metadata schema mapping

Configure folder metadata mapping

Metadata mapping between Workfront Projects and AEM Folders is defined within AEM Folder Metadata Schemas. Folder Metadata Schemas should be created and configured as usual in AEM. Workfront Tools adds an autocomplete dropdown to the Settings configuration tab of each folder metadata schema form field. This autocomplete drop- down menu will allow you to specify to which Workfront field each AEM folder property should be mapped to.

To configure the mappings, follow these steps:

1. Navigate to Tools > Assets > Folder Metadata Schemas.

2. Select the folder metadata schema form you wish to edit and click Edit.

3. Select the folder metadata schema form field you wish to edit and select Settings tab on the right panel.

4. In Mapped from Workfront Field field, select the name of the Workfront field that you wish to map to the selected AEM folder property. Available options are:

   • Project custom form fields
   • Project Overview fields (ID, Name, Description, Reference Number, Planned Completion Date, Project Owner, Project Sponsor, Portfolio or Program)

Configure asset metadata mapping

Metadata mapping between Adobe Workfront Documents and Assets is defined within AEM Metadata Schemas. Metadata Schemas should be created and configured as usual in AEM. Workfront Tools adds configuration options to the Settings configuration tab of each metadata schema form field. These options will allow you to specify to which Workfront field each AEM property should be mapped to.

To configure the mappings, follow these steps:

1. Navigate to Tools > Assets > Metadata Schemas.

2. Select the metadata schema form you wish to edit and click Edit or create a new metadata schema from scratch.

3. Select the metadata schema form field you wish to edit and select Settings tab on the right panel.

4. In Workfront Custom Form Field select the name of the Workfront field that you wish to map to the selected AEM property. Available options are:

   • Document custom form fields
   • Project custom form fields
   • Issue custom form fields
   • Task custom form fields
   • Project Overview fields (ID, Name, Description, or Reference Number)

5. In the case where the Workfront field selected in Workfront Custom Form Field is a Workfront User type-ahead field, it will be necessary to specify which Workfront User field you wish to map. To do so, check Get value from Workfront referenced object field and then specify the name of the Workfront User Custom Form Field from which to retrieve the value to be mapped.

   

Map property

This workflow step lets a user map a property to a Workfront custom form on a project, task, issue, or document. The Workfront artifact this step affects is looked up using a relative path from the payload. The properties to be mapped are controlled from within the steps dialog configuration.

Type: This field lets you select the Workfront object type that the properties should be mapped to.

ID Property: This field lets you specify the path to the ID of the Workfront object that the properties should be mapped to. The path specified in this field should be relative to the workflow payload.

Property Assignments: This multifield lets you specify the mappings between AEM properties and Workfront fields. Each item in the multi-field will specify one mapping. Each mapping should have the format <workfront-field>=<aem-mapped-property>.

• The workfront-field can be

  • A custom form field identified by the prefix DE:.
  • An editable field identified by its name. The field names are found in Workfront API explorer.

• The aem-mapped-property can be:

  • A literal value. These should be surrounded by quotation marks.
  • An AEM property. This reference should be relative to the workflow payload.
  • A named value. These should be surrounded by brackets.
  • A concatenation of the above 3 items. Specify it using {+}.
  • An alteration of the above 3 items by surrounding the value with {replace(<value>,”old-char”,”new-char”)}.

• Some example are:

  • status="INP"
  • DE:Asset Type=jcr:content/metadata/assetType
  • DE:Path={path}
  • URL=”https://my-aem-author/assets.html”{+}{path}

Set status

In workflow editor, edit the properties of Workfront - Set Status in the Arguments tab.

Comments synchronization

1. In Experience Manager, access Tools > Cloud Services > Workfront Tools Configuration, select the configuration, and select Properties.

   

2. Select Event Subscriptions tab, click Enable Comment Sync on Send Comments made in Workfront to AEM option.

   

To test the synchronization of comments from Workfront to AEM, follow these steps:

1. Navigate to a linked document in Workfront and add a comment in the Updates tab.

   

2. Navigate to the same linked document in AEM, select the document and open the Timeline option in the left navigation, and select Comments. The left sidebar displays the comments synchronized from Workfront.

Asset versions

To maintain version history of assets in AEM, configure asset versioning in AEM.

1. In Experience Manager, access Tools > Cloud Services > Workfront Tools Configuration, and open the Advanced tab.

2. Select option Store assets with the same name as versions of the existing asset. When checked, this option enables storing assets uploaded with the same name and to the same location as the version of the existing asset. If left unchecked, a new asset will be created with a different name (for example, asset-name.pdf and asset-name-1.pdf).

3. Select option Update asset metadata when creating a new version. When checked, this option updates the asset metadata whenever a new version of the asset is created. If unchecked, the asset will keep the metadata it had prior to creating the new version.

Attach custom forms

This workflow step lets users attach a custom form to a Workfront artifact. This workflow step can be added to any workflow model. The Workfront artifact this step affects will be looked up using a relative path from the payload.

In workflow editor in Experience Manager, edit the properties of the Workfront - Attach custom form workflow step.

.

Auto-publish assets

1. In Experience Manager, access Tools > Cloud Services > Workfront Tools Configuration, and open the Advanced tab.

2. Select Automatically publish assets when sent from Workfront. This option enables automatic publishing of assets when they are sent from Workfront to AEM. This feature can be enabled conditionally by specifying a Workfront custom form field and the value it should be set to. Whenever a document is sent to AEM, if it satisfies the condition, then the asset will be automatically published.

3. Select Publish all project assets to Brand Portal upon project completion. This option enables automatic publishing of assets to Brand Portal when the status of the Workfront project they belong to is changed to Complete.

Workfront document custom form updates

To subscribe to the changes in Workfront document custom forms, select the relevant option in the Advanced tab. When you subscribe to these updates, it updates your mapped Experience Manager metadata fields when the corresponding field in Workfront document custom form is changed.

Business.Adobe.com resources