AD0-E906 Adobe Workfront for Experience Manager enhanced connector Expert Questions and Answers

To configure the Enhanced Connector in AEM, including features like automatic project-linked folder creation, comment syncing, and automatic publishing of assets, you should navigate to:

Tools > Workfront Tools > Workfront Tools Configuration: This is where you can access and configure the connector settings within AEM. From there, selecting the configuration and choosingPropertiesin the action bar allows you to adjust the required settings.

Options B and C reference incorrect paths (Cloud Services and Assets), which are not used for the Enhanced Connector configuration.

Refer toAEM’s Enhanced Connector documentationfor step-by-step instructions on accessing and configuring the connector.

In this scenario, the best approach is to create separategroupsfor Marketing and IT within the same Workfront instance. Each group will have its owngroup administrator, and each department’s resources (e.g., custom statuses, templates, reports) can be isolated and managed independently by the group admins.

This solution ensures that:

Theexisting IT setupis not disrupted.

The Marketing department can have its own customized Workfront environment without overlapping with IT's configurations.

This approach avoids creating unnecessary complexity (as in Option A with companies) or restricting functionality (as in Option B with teams).

Refer toWorkfront documentation on group managementto learn how to implement group-specific configurations in a single instance.

In this scenario, the calculated fieldAllowable Daysand theRequired Delivery Dateneed to display on the project. To achieve this:

Allowable Days: This is a calculated field, so it should be set up as a calculated field in the project custom form, which references the difference between theRequest Entry Dateand theRequired Delivery Date.

Required Delivery Date: This is a static field and should be displayed as a text field to ensure that the original requested delivery date is retained.

Option B is incorrect because both fields do not need to be calculated. TheRequired Delivery Dateis already a static value and doesn’t require calculation.

For more information, refer to theWorkfront documentationon setting up calculated fields and text fields in custom forms.

The requirement is to allow users to select a resource (Creative Manager) from a list of existing users in the Workfront application. The appropriate solution is to use aTypeahead fieldwith theUser object type.

Field type - Typeahead: This field allows users to start typing the name of an individual, and the system will auto-suggest matching users from the Workfront database. This is ideal for scenarios where you need to assign a specific role, like a Creative Manager, from a list of existing users.

Object type - User: By using the User object type, the field will link directly to Workfront's user directory, ensuring that the selection is limited to valid, active resources in the system.

This combination of field and object type is the most efficient for assigning roles based on existing users, as it prevents errors and ensures data consistency by utilizing Workfront’s internal user directory.

Options B and C are not suitable because acalculated fieldis not required, andcheckboxesdo not allow selection from a list of user names.

For further reference, consult theCustom FieldsandTypeahead Fieldssections in Workfront’s documentation, which outline how to configure these fields to enable user selection from the organization’s resource pool.

In Workfront, the best way to ensure that all documents within a project are shared with a designated team is toshare the entire project. By sharing the project, all documents and related assets within that project are automatically made available to the designated team members according to the project's access permissions.

Option C is incorrect because sharing one document does not automatically inherit the same access levels for the other documents. Option A suggests linking documents from AEM, but the question pertains to sharing documents within Workfront itself.

Refer to Workfront’sdocumentation on document sharingfor detailed instructions on how to share all project-related assets with teams.

To implement conditionalautomatic publishingof assets from Workfront to AEM based on the value of the custom form field, you should:

Check the option "Automatically publish assets when sent from Workfront": This ensures that the assets will be automatically published to AEM when they are sent from Workfront.

Use the custom form field ("auto_publish_assets"): The system needs to check the value of this custom form field, and if it is set to"Yes", the assets will be automatically published.

Set the Custom Form Field Value to "Yes": In the configuration, you’ll specify that automatic publishing only occurs when the field value is "Yes."

Option B incorrectly refers to "Workflow" instead of "Workfront," and Option C refers to publishing to Brand Portal, which is irrelevant since the customer does not have Brand Portal.

Refer toWorkfront for AEM Enhanced Connector documentationfor step-by-step guidance on configuring conditional automatic asset publishing.

To enable the search of products by SKU number in AEM, two main configurations are required:

Multi Value Property Predicate: By using a Multi Value Property Predicate, users can search for multiple SKU numbers at once. This is crucial if product owners need to query for multiple products simultaneously.

Single Line Text Field for SKU: SKU numbers are typically unique, so adding aSingle Line Text fieldto the image metadata schema for SKU numbers ensures that each image has its own SKU field for accurate identification during searches.

Option D is incorrect because SKUs are usually single, unique identifiers, so a Multi Value Text field isn’t necessary for each SKU.

Refer to AEM’sdocumentation on customizing metadata schemasandAssets Admin Searchto implement these features.

TheAuthorpermission role is necessary for the design team members who need toedit the proofsbefore they are sent for review by legal and financial teams. This role allows them to make changes directly to the proof and upload new versions, which is essential for their work in this multi-stage automated workflow.

Author role: Grants permission to edit and manage the proof, which includes uploading new versions and making changes to the existing proof content.

Options B (Reviewer) and C (Approver) are more restrictive roles that do not allow for editing proofs.

Refer toWorkfront Proofing roles and permissions documentationfor more information on the different proof roles.

In this scenario, the user is managing a marketing campaign in Workfront and wants to use an existing asset from AEM Assets. Since the enhanced connector is already installed and configured, the user can go to theDocumentsarea within the Workfront project, clickAdd new, and then select theExperience Manager integration.

This integration allows the user to browse assets stored in AEM and select the required asset, which will be linked to the Workfront project without the need to download and re-upload the file.

This seamless integration between Workfront and AEM Assets enhances workflow efficiency by enabling users to directly access and use assets from AEM within their Workfront environment.

For more information, refer to the documentation onWorkfront and AEM Asset Integration, which covers the process of selecting and using AEM-stored assets within Workfront.

In this scenario, the company is looking to group projects based on a benefit calculation from a custom form. The most efficient way to achieve this grouping and reporting structure in Adobe Workfront is by creating avalue expressionon the view. This method allows you to dynamically link the benefit value from the request object to other reporting structures, including the project object.

Value Expression on View:The value expression acts as a direct link between the custom form's calculated field and the reporting or view settings, enabling the system to pull the benefit value dynamically from the request.

Request Object Linking:By linking to the source request object through the value expression, it allows for seamless integration of calculated values into the project reporting view, ensuring that the benefit groups (Level 1-4) can be reported accurately based on the defined thresholds (0, 1-5, 6-10, 11-15).

This approach is more efficient compared to creating multiple calculated fields across different objects, and it allows for better maintainability and adaptability in future changes.

References from Adobe Workfront documentation emphasize the use ofvalue expressionsin reports and views for linking and utilizing calculated fields across different objects, enhancing the flexibility and power of custom reporting capabilities. Text mode is not necessary here because it is primarily used for custom formatting or more advanced use cases that don't involve simple value transfers between objects.

For more detailed information, you can refer to the official Workfront Help documentation onCustom FormsandAdvanced Reporting Techniquesin Adobe Workfront, where calculated fields and value expressions are thoroughly covered.

In the given scenario, the developer needs to execute a Maven profile specifically for theCloud Manager deployment pipeline. This requires the use of a property that is exclusive to Cloud Manager, allowing the profile to activate only when the build is being executed in the Cloud Manager environment.

Option C uses the correct activation property:

env.cloudmanager

This property is specific to Adobe's Cloud Manager environment, ensuring that this Maven profile will only be activated during Cloud Manager deployments. This allows the local deployment process to remain unaffected while the correct profile is triggered in Cloud Manager.

Options A and B use other properties (env.CM_BUILD or CM_BUILD) that are not standard or specific to the Cloud Manager environment, making them incorrect choices.

For more details, you can refer to Adobe’sCloud Manager Maven Configurationdocumentation, which outlines how to configure Maven profiles specifically for Cloud Manager's deployment pipelines.

When configuring theWorkfront for Experience Manager Enhanced Connectorto version files correctly in AEM, the following criteria must be met:

Same Name: The new version of the file must have the exact same name as the current version. This ensures that AEM recognizes the file as a new version of an existing asset rather than a completely new asset.

Same Location: The new version must be sent to thesame locationin AEM as the current version. If the file is uploaded to a different location, AEM will not recognize it as a version of the existing asset.

Option B (appending version numbers) is not required for versioning in AEM, as versioning is handled internally based on the file’s name and location. Option C (same metadata) is not necessary for versioning but could be relevant for other workflows or metadata synchronization.

Refer toAEM Enhanced Connector documentationfor detailed instructions on configuring versioning and asset management between Workfront and AEM.

When metadata mappings between Adobe Workfront and AEM are configured, the process of sending a document along with its metadata from Workfront to Adobe Experience Manager (AEM) Assets is streamlined. The user selects the document in Workfront, clicks "Send to," and chooses the Experience Manager integration.

The metadata fields that have been mapped are automatically synchronized along with the document. There is no need for manual selection of metadata at this stage, as the integration ensures that all configured mappings are applied.

This functionality is part of the enhanced connector, which simplifies the workflow between Workfront and AEM Assets by automating the synchronization of mapped metadata fields during the document transfer.

For more details, refer to Adobe's documentation onWorkfront for Experience Manager Enhanced Connector, which outlines how automatic metadata synchronization works during document transfers.