In this case, the solutions consultant needs to limit the legal team’s access to read-only for all content in AEM. Since the legal team will be working in Workfront and accessing AEM via the enhanced connector, the best way to manage their access is to apply Access Control Entries (ACEs) to the wf-workfront-users user group.

ACEs allow you to specify detailed permissions for a group or user in AEM, such as granting read-only access to specific resources or folders within the DAM.

Options A and C would either grant too much access (as in the case of the Everyone user group) or allow contributions, which is beyond the requirement of just reading access.

Refer to AEM Access Control Management documentation to learn more about setting up ACEs and managing permissions.

In AEM, to limit the number of concurrent workflows running at the same time, you need to adjust the Maximum Parallel Jobs setting in the OSGI console. This setting controls how many workflow jobs can be processed simultaneously, and reducing this number will lower the load on the server by limiting the number of workflows that can run concurrently.

This setting can be found under the Day CQ Workflow - Workflow Engine configuration in the OSGI Web Console.

Options B and C refer to specific workflows and threads, but they do not directly address the overall system limit on concurrent workflow executions.

Refer to the AEM documentation on workflow scaling and performance for more information on how to adjust these settings in the OSGI configuration.

In this scenario, the best approach is to create separate groups for Marketing and IT within the same Workfront instance. Each group will have its own group 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:

The existing IT setup is 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 to Workfront documentation on group management to learn how to implement group-specific configurations in a single instance.

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.

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.

The features requested by the customer, such as automatic folder creation, synchronization of Workfront document custom form values to AEM asset metadata, and automatic publication of assets to Brand Portal upon project completion, rely on Event Subscriptions in the enhanced connector configuration.

Event Subscriptions are triggered when certain events occur, such as project completion or updates to custom form values, ensuring that the correct actions (like folder creation or asset publication) happen automatically.

Option A (Workflows) would be used for content approval processes but not for these specific automatic actions. Option B (Webhooks) can handle external notifications but is not directly relevant for these tasks within AEM and Workfront.

For more information, refer to AEM Enhanced Connector documentation on Event Subscriptions and their use in automating processes.

In this scenario, the reviewer needs to leave comments on an interactive web content URL and tag the designer. The Web Proofing viewer is the appropriate tool for reviewing interactive web content in Adobe Workfront. The Web Proofing viewer allows users to:

Review and comment on web-based content directly in the browser.

Tag users in comments and updates.

Approve or reject the content with the necessary feedback.

Option A (Desktop Proofing viewer) is typically used for offline or downloadable content, and Option C (Legacy Proofing viewer) refers to an outdated tool that lacks modern proofing functionalities.

Refer to Workfront’s proofing documentation for more information on using the Web Proofing viewer for interactive content.

When configuring the Workfront Enhanced Connector in AEM, Workfront users who will use the connector are automatically added to a corresponding AEM user group via the connector. This automatic process ensures that permissions and group assignments are correctly synced between Workfront and AEM without manual intervention.

Option A (using the Import People option in Workfront) refers to importing users into Workfront, not syncing users to AEM. Option C (from the Adobe Admin Console) is related to managing users in the Adobe platform but not specifically for the Enhanced Connector.

Refer to AEM and Workfront Enhanced Connector documentation for more information on user synchronization and group management.

To upload a new version of a document and ensure it is available in AEM Assets, the user must select the New Version option in Workfront. This triggers the version control process where the updated file can be uploaded.

By choosing the Experience Manager integration after selecting New Version , the system ensures that the latest version of the document is sent to AEM Assets, where it will replace the previous version without losing version history.

This workflow supports maintaining version control between Workfront and AEM, ensuring that the most current version of the asset is always available in both systems.

Refer to the Workfront-AEM Enhanced Connector Guide for further details on version control and document updates between Workfront and AEM.

In this scenario, the calculated field Allowable Days and the Required Delivery Date need 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 the Request Entry Date and the Required 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. The Required Delivery Date is already a static value and doesn’t require calculation.

For more information, refer to the Workfront documentation on setting up calculated fields and text fields in custom forms.