AD0-E906 Exam Dumps : Adobe Workfront for Experience Manager enhanced connector Expert

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 theAdobe Workfront Form Customization Guide.

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

InOption 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’scontent-typeandeffortmetadata 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 theWorkfront Enhanced Connector documentationfor detailed instructions on configuring metadata synchronization between AEM and Workfront.

Thejavax.jcr.PathNotFoundExceptionin 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 aPermissionDeniedException, 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 theAEM documentation on handling assets and JCR path exceptions.