Adobe AD0-E908 Practice Test - Questions Answers, Page 2

Project status and timesheets:

For tasks to appear on a timesheet, the project status must be set to 'Current.' If the project status is anything other than Current (e.g., Planning, Complete, or On Hold), tasks from that project will not automatically populate the timesheet.

Inherited status names:

Sub-groups inherit the project status names from their parent group unless explicitly overridden. Therefore, the AP sub-group under the Finance group will use the same custom project status names assigned to the Finance group.

Converting an issue to a task:

Issues can be converted into tasks within a project. This allows for better tracking and management of the work required to resolve the issue.

Converting an issue to a project:

Issues can also be converted into standalone projects. This is useful when an issue requires a series of tasks and resources that warrant its own project structure.

In Adobe Workfront, the hierarchical relationship between Queue Topics and Topic Groups is that Topic Group is the parent, and Queue Topic is the child. This means that a Topic Group can contain multiple Queue Topics, but a Queue Topic is always part of a Topic Group. This structure helps organize and categorize different types of requests or issues within Workfront, making it easier to manage and track them.

Reference

The hierarchy between Queue Topics and Topic Groups is frequently highlighted in Workfront documentation and training materials, reinforcing that Topic Groups serve as the broader category under which specific Queue Topics fall.

In Adobe Workfront, Custom Forms can be shared by their authors with specific permissions. The author of a Custom Form has the ability to control who can view, share, and edit the form. These permissions can be set for individuals, roles, groups, teams, and even across the entire company. This functionality is critical for maintaining control over who can access and modify the forms, ensuring that only authorized users have the appropriate level of access.

Reference

This information is consistent with the permissions settings outlined in the Workfront documentation and in various training resources provided by Adobe.

When building a custom form in Adobe Workfront that uses display logic and skip logic, developers need to consider the following:

When copying an old form: If you copy an existing custom form that includes display logic or skip logic, these logic settings will not be transferred to the new form. The logic needs to be manually recreated in the new form to ensure it functions as intended.

Skip logic limitations: Skip logic does not operate effectively with certain elements like widgets or section breaks within the form. This limitation means that skip logic cannot be applied to control the visibility or behavior of these elements, potentially impacting how the form is structured and functions.

Reference

These considerations are detailed in advanced reporting and form customization documentation and have been highlighted in various Workfront admin training sessions.

Request queues in Adobe Workfront are particularly useful for managing the intake of work requests into a department. By setting up a request queue, a team can standardize the process for receiving, evaluating, and assigning incoming requests. This helps in ensuring that all requests are handled consistently and efficiently, prioritizing and delegating work based on the team's capacity and current workload.

Reference

The usage of request queues for managing work intake is a common practice outlined in Workfront training materials and is emphasized in several case studies and user guides provided by Adobe.

Objective: Ensure that everyone in the organization can fill out the general project custom form associated with the general project template.

Form Sharing Settings:

Correct Setting: Update the form sharing to 'Make this visible system-wide so that everyone in Workfront can see it'.

Objective: Track project metrics based on the submitted request without allowing the requester to fill in this information.

Configuration Steps:

Step 1: Create a Custom Form with the necessary metric fields.

Step 2: Do not include these metric fields in the part of the form visible to the requester.

Step 3: Add these metric fields to the project details section instead.