A team has just created a new project template. Before making the template active, the team needs to ensure that users have access to use the template and the projects created from the template.
Which two items must be configured to achieve this requirement? (Choose two.)
Objective: Ensure users have access to use a new project template and the projects created from it.
Configuration Steps:
Step 1: Configure Project Sharing
Step 2: Configure Template Sharing
A client requires that employees account for any "breaks" during their day in order to report on utilization. How would a System Administrator configure this requirement?
Identify the Requirement: The client needs to track 'breaks' during the employees' workday to report on utilization. This requires a way for employees to log their break times accurately.
Understand Workfront's Time Tracking Capabilities: Workfront allows the creation of different hour types which can be assigned to timesheets. This flexibility helps in categorizing time entries for various activities, such as work, meetings, training, and breaks.
Creating a 'Break' General Hour Type:
Navigate to Setup: As a system administrator, go to the Setup area in Workfront.
Access Hour Types: Under the 'Timesheets & Hours' section, select 'Hour Types'.
Add New Hour Type: Click on the option to add a new hour type.
Define Hour Type: Name the new hour type as 'Break'. You can provide a description for clarity. This will help users understand that this category is specifically for logging break times.
Save the Hour Type: Ensure to save the new hour type so that it becomes available for timesheet entries.
Assigning the 'Break' Hour Type to User's Timesheet Profile:
Navigate to User's Profile: Go to the user's profile settings.
Edit Timesheet Profile: Within the profile, locate the section for timesheet settings.
Add Hour Type: Include the newly created 'Break' hour type to the list of available hour types that users can select when logging their hours.
Save Changes: Ensure that all changes are saved so users can start using the 'Break' hour type in their timesheets.
Implementation and Training:
Communicate with Users: Inform users about the new 'Break' hour type and provide instructions on how to log their break times in their timesheets.
Monitor Utilization: Track the usage of the new hour type to ensure that it is being utilized correctly and effectively for reporting purposes.
A project team has configured a Kanban board with columns for backlog, in progress, on hold, and completed statuses. The project manager wishes to automatically archive cards that have been closed for longer than two weeks.
What should the project manager change in order to make this happen?
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.
What are the constraints among Programs, Portfolios. Tasks, and Projects?
In Adobe Workfront, there are specific constraints regarding the association of projects, programs, portfolios, and tasks. A project and its tasks can only belong to one portfolio and one program at a time. This means that a single project cannot be simultaneously associated with multiple portfolios or programs. This constraint ensures clear and unambiguous project management and reporting within the organizational structure.
An engineering team works with an outside vendor who occasionally needs to review and approve documents in Workfront Proof. Which built-in access level would be assigned to the vendor9
Objective: Assign the appropriate access level to an outside vendor who needs to review and approve documents in Workfront Proof.
Access Level:
External User: This access level is designed for external collaborators who need limited access to review and approve documents without full access to all internal resources.
