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

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 a value expression on 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 of value expressions in 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 on Custom Forms and Advanced Reporting Techniques in Adobe Workfront, where calculated fields and value expressions are thoroughly covered.

In Workfront, the best way to ensure that all documents within a project are shared with a designated team is to share 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’s documentation on document sharing for detailed instructions on how to share all project-related assets with teams.

The javax.jcr.PathNotFoundException in this case indicates that the path to the asset /content/dam/projectA/asset.jpg cannot be found. The most likely cause is that the asset does not exist at the specified location, and thus the AssetManager is unable to copy it.

PathNotFoundException : This exception is thrown when the repository path (in this case, the asset path) is not found in the JCR repository, meaning that the asset does not exist or the path is incorrect.

Other possibilities like permissions issues (Option C) would typically result in a PermissionDeniedException , and Option B is incorrect because the issue specifically pertains to the asset path, not the parent folder.

To resolve this, the developer should check if the asset exists at the specified path or if the path is misspelled. For more information, refer to the AEM documentation on handling assets and JCR path exceptions .

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 a Typeahead field with the User 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 a calculated field is not required, and checkboxes do not allow selection from a list of user names.

For further reference, consult the Custom Fields and Typeahead Fields sections in Workfront’s documentation, which outline how to configure these fields to enable user selection from the organization’s resource pool.

When converting a request to a project in Adobe Workfront, it's important to ensure that custom fields and their values are correctly passed from the request form to the project form. To achieve this, you need to add the same custom field on the project form, but in this case, the calculation should be left blank because the calculated value from the request form will be passed over and does not need to be recalculated at the project level.

Same field : The field needs to be exactly the same (same internal name) so the data can flow between the request and the project during the conversion.

Blank calculation : By leaving the calculation blank, you ensure that the field will accept the value from the request without overriding it or attempting to recalculate it.

For more details on setting up custom forms in Workfront and handling calculated fields during request-to-project conversions, refer to the Adobe Workfront Form Customization Guide .

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 a Single Line Text field to 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’s documentation on customizing metadata schemas and Assets Admin Search to implement these features.

To synchronize comments on linked documents from Adobe Workfront to Adobe Experience Manager, you need to enable Workfront Event Subscriptions in the enhanced connector configuration properties. Event Subscriptions allow AEM to track changes and updates from Workfront, including comment synchronization.

Workfront Event Subscriptions ensure that comments made in Workfront on linked documents are automatically synced to AEM.

Option A incorrectly references the Advanced tab, and Option C incorrectly states "Unable" instead of "Enable" Comment Sync.

Refer to AEM Enhanced Connector documentation on Event Subscriptions for step-by-step configuration.

To ensure that changes in metadata in Adobe Experience Manager (AEM) are synced back to Workfront for the fields Content Type and Effort , the correct property assignment should map the Workfront custom form fields to the corresponding paths in the AEM JCR repository.

In Option A :

CUSTOM FORMS

is mapped to /jcr:content/metadata/content-type

CUSTOM FORMS

is mapped to /jcr:content/metadata/effort

This configuration ensures that changes made in AEM’s content-type and effort metadata properties will be reflected in the respective custom fields in Workfront.

Options B and C use incorrect prefixes (e.g., "DE:") and would not map the properties correctly for synchronization between Workfront and AEM.

Refer to the Workfront Enhanced Connector documentation for detailed instructions on configuring metadata synchronization between AEM and Workfront.

The requirement is to deploy the com.myCompany.ui.content package specifically to the AEM Cloud Service author environment. The key here is ensuring that the package is targeted correctly to the author instance, without affecting other environments.

Option A uses the following target:

< target > /apps/my-company-packages/content/install.author < /target >

The use of install.author ensures that the package will only be installed on the author environment of AEM as a Cloud Service, meeting the developer's requirement. This is a common approach in AEM Cloud Service projects, where you differentiate between environments using the appropriate subfolder (in this case, author).

Option B (author.install) and Option D are similar but incorrect because they are not standard for specifying the exact environment, while Option C (install/) is too generic and could apply to both author and publish environments.

Refer to the AEM Cloud Service documentation on deployment and package management for more details on targeting specific environments such as author during content deployment.

Workfront includes a document checkout feature that allows users to lock a document when it is being edited, preventing others from downloading or editing the file simultaneously. This feature effectively stops duplication of effort and ensures that only one person can work on a document at a time.

Document Checkout : By navigating to the document details page and clicking "Check out," the document will be locked for editing by the person who checked it out. Other users will be notified that the document is being edited, and they will not be able to download or make changes until it is checked back in.

Option B is incorrect because changing the document status to "Unavailable" does not prevent downloading or editing. Option C, while helpful for communication, does not enforce restrictions, which could still lead to duplication of effort.

For more detailed information, refer to the Document Collaboration and Management section in the Adobe Workfront documentation, which outlines how the check-in/check-out system works.

In Adobe Experience Manager (AEM) as a Cloud Service, deployments are handled through Cloud Manager, and all code, including third-party libraries, must be part of the versioned code repository. To deploy the third-party package provided by the vendor, it needs to be included as part of the AEM project’s codebase under the install folder within the repository:

The package should be stored in the < url > file;$(maven.multiModuleProjectDirectory)/install < /url > directory.

Once stored, the deployment will be handled through Cloud Manager’s deployment pipeline.

This ensures the third-party package is included in the standard deployment process and follows AEMaaCS's immutable infrastructure model, which ensures that changes to environments are made only through deployments using Cloud Manager.

Option B is incorrect because installing a package directly to production via CRX Package Manager is not allowed in AEM as a Cloud Service. Option C would work for self-hosted AEM instances but not for AEMaaCS, where dependencies must be part of the Maven build.

For more information, refer to AEMaaCS deployment best practices and the Cloud Manager documentation .

In this scenario, the workflow launcher is configured to trigger a workflow for assets in the path /content/dam/projects/en/designs. However, to ensure that the workflow only triggers for image assets, the condition must be updated to filter the relevant asset types. The condition should be modified to dc:format==image/*, which ensures that only assets with an image format trigger the workflow.

Condition "dc

==image/*" : This filters assets based on their format (MIME type), ensuring that the workflow is only triggered for images, which matches the use case of working with assets such as JPGs or PNGs.

Option B suggests modifying the path, but the existing path (/content/dam/projects/en/designs) is correct for the project structure. Option C suggests changing the node type to nt:file, which is incorrect since the node type for assets in AEM is typically dam:Asset.

For more information, refer to AEM documentation on workflow launchers and DAM metadata properties .

In this scenario, the proofing workflow needs two stages:

Stage 1 : This stage routes the proof to the creative director upon proof creation. By selecting "do not allow this stage to be deleted," the workflow ensures that the creative director must always review the proof before it is sent to stakeholders. This ensures consistency in the review process and makes sure the creative director is always involved.

Stage 2 : This stage activates when all decisions are made on the parent stage (i.e., the creative director’s approval). Additionally, since the creative agency only requires one decision from each company , the "only one decision required" setting is appropriate to speed up the process while ensuring the necessary approvals are gathered.

Option B is incorrect because setting the stage as private may hinder collaboration, and Option C suggests waiting until all decisions are approved, which is not necessary in this scenario.

Refer to Workfront documentation on proofing workflows for details on setting up multi-stage approval processes.