Adobe AD0-E908 Practice Test - Questions Answers

In Adobe Workfront, time can be recorded on Projects, Tasks, and Issues. This flexibility allows users to track time spent on various types of work items, providing comprehensive time management and reporting capabilities.

Record Time on Projects:

Navigate to a project.

Click on the 'Hours' tab.

Enter the time spent on the project.

Record Time on Tasks:

Navigate to a task within a project.

Click on the 'Hours' tab.

Enter the time spent on the task.

Record Time on Issues:

Navigate to an issue within a project.

Click on the 'Hours' tab.

Enter the time spent on the issue.

The processes for recording time on various objects are detailed in the Workfront time-tracking documentation and training materials (Advanced Reporting - Monique Evans - Code Snippet - June 2, 2020).

When an issue with a document attached is moved to a different project in Adobe Workfront, the document and any approvals associated with it will also move to the new project along with the issue. This ensures that all related information and approvals are retained and correctly associated with the issue in its new context.

Move the Issue:

Navigate to the issue that needs to be moved.

Select the option to move the issue to another project.

Verify Document Movement:

After moving the issue, check the new project to ensure the document is correctly associated with the issue.

Verify that any approvals linked to the document are also moved and remain intact.

This behavior is confirmed in the Workfront documentation and issue management training guides, which explain how documents and approvals are handled when moving issues (Workfront Training Deck - Worker 2.15.23).

The Reviewer & Approver role allows the user to provide a final decision on the proof, which includes options like Approve, Changes Needed, or Not Relevant. This role is ideal for those who need to summarize their overall feedback and make a conclusive decision.

Notification upon approval:

By assigning the Reviewer & Approver role, the user is notified when an approval decision is made on the proof. This ensures that they are kept in the loop and can follow up as necessary.

Identify the Requirement: The admin needs to set up an Automated Workflow Template and ensure that the design team can view the new templates.

Understanding Sharing Mechanisms in Workfront: Workfront allows administrators to share templates, projects, and reports with specific users or groups to ensure visibility and collaboration.

Creating the Automated Workflow Template:

Navigate to Templates: In Workfront, go to the Templates section.

Create New Template: Select the option to create a new workflow template.

Define Workflow: Set up the workflow steps, including tasks, approvals, and dependencies, as required for the design team's processes.

Save the Template: Ensure the workflow template is saved correctly in the system.

Sharing the Workflow Template:

Select the Template: Go to the created workflow template in the Templates section.

Share with Design Team: Use the sharing options to specifically share the template with the Design Team group. This ensures that only the design team has access to the new workflow template.

Set Permissions: Define the level of access the design team will have, such as view, edit, or manage permissions.

Communication and Training:

Notify the Design Team: Inform the design team about the new workflow template and how they can access and use it.

Provide Training: Offer training sessions or materials to help the design team understand how to use the new automated workflow template effectively.

Identify the Requirement: The differences between tasks and issues need to be clarified.

Understanding Tasks and Issues in Workfront:

Tasks: Represent planned work and are created within projects. They have specific start and end dates, assigned resources, and dependencies.

Issues: Represent unplanned work that arises and needs to be addressed. Issues can be created within projects or as standalone items and often require immediate attention.

Key Differences:

Creation:

Tasks: Can only be created within the context of a project. They are part of the project's planned workflow and structure.

Issues: Can be created within projects or attached to tasks. They provide a way to log unplanned work or problems that need resolution.

Nature of Work:

Tasks: Represent planned, scheduled work that follows the project timeline and milestones.

Issues: Represent unplanned, often urgent work that needs to be addressed outside of the planned workflow.

Identify the Requirement: The customer wants to use custom statuses for project tasks, but not all users need to use these statuses.

Creating Custom Statuses:

Navigate to Setup: Go to the Setup area in Workfront.

Custom Statuses: Within the Setup area, select 'Statuses'.

Create New Status: Add new custom statuses that are relevant to the project's workflow stages.

Associating Custom Statuses with Groups:

Select Group: Identify the group associated with the projects that need these custom statuses.

Assign Statuses to Group: In the Group settings, assign the newly created custom statuses. This ensures that only users within this group will have access to and can use these statuses.

Implementation and Training:

Communicate with Users: Inform the relevant users about the new custom statuses and how they will be used within their projects.

Provide Training: Offer training to ensure users understand how and when to use the custom statuses appropriately.

Identify the Requirement: The admin notices that the custom task status is only available in some projects with assigned Marketing team members.

Understanding Group Statuses: Group statuses in Workfront are linked to specific groups and are only available in projects that are associated with those groups.

Review Project Details:

Check Project Association: Ensure that the projects where the status is missing are correctly associated with the Marketing group.

Update Project Details: If necessary, update the project details to associate them with the Marketing group. This will ensure that the custom group statuses are available.

Implementation:

Verify Group Settings: Confirm that the custom statuses are correctly set up for the Marketing group in the group settings.

Communicate with Users: Inform project managers and team members about the association requirements for using custom group statuses.

Identify the Requirement: The project manager wishes to automatically archive cards that have been closed for longer than two weeks on a Kanban board.

Understanding Card Falloff in Workfront: Workfront allows for the configuration of automatic archiving (card falloff) based on the time a card has been in a specific column. This is useful for maintaining a clean and organized Kanban board.

Steps to Configure Card Falloff:

Navigate to the Board: Go to the Kanban board where the columns for backlog, in progress, on hold, and completed statuses are set up.

Access Configuration: Click on 'Configure' to access the board settings.

Select Cards: In the configuration settings, go to the 'Cards' section.

Enable Card Falloff: Enable the option for card falloff and set it specifically for the 'Closed' column. Set the falloff duration to two weeks.

Implementation:

Apply Settings: Save the configuration changes to ensure that cards in the Closed column will automatically archive after two weeks.

Monitor: Regularly check to ensure that the card falloff is functioning as expected and that closed cards are being archived after the specified time.

Identify the Requirement: The project manager wants to track specific types of issues with additional custom fields for each type within a project.

Understanding Queues and Custom Forms in Workfront: Workfront allows the creation of queues to manage different types of requests or issues. Queue topics can be used to categorize these issues, and custom forms can be applied to capture additional information specific to each issue type.

Steps to Create a Queue with Custom Forms:

Navigate to the Project: Go to the project where you want to track specific issues.

Create a Queue: In the project settings, create a queue.

Define Queue Topics: Set up queue topics to represent the different types of issues (e.g., Bug Reports, Change Requests, etc.).

Assign Custom Forms: Create custom forms with the necessary fields for each issue type and assign them to the corresponding queue topics.

Implementation:

Setup Custom Fields: Ensure the custom fields on the forms are configured correctly to capture all required information.

Test the Queue: Test the queue by creating sample issues to ensure that the custom forms are working as expected for each issue type.