Changing a group-specific approval process from one group to another

The following scenarios occur when a group-specific approval process is already being used on an object and someone reassigns it to a different group:

Area or object where the approval process was attachedApproval objectChange in the approval process for the object or area
Project or template approvalProjectBecomes a single-use approval process
Task or template task approvalTaskBecomes a single-use approval process
Issue approvalIssueBecomes a single-use approval process
Tasks area in the Edit Project or Edit Template boxTask

The Task Default Approval Process field is reset to N/A.

By default, no approval processes are associated with new tasks on the project.

Queue Details section of a project or templateIssue

The Default Approval field is reset to N/A.

By default, no approval processes are associated with new issues or requests on the project.

Queue Topic section of a project or templateIssue

The Default Approval field is reset to N/A.

No approval processes are associated with new issues or requests on the project by default.

Changing the group associated with a project

When someone changes the group associated with a project to different group, the following occurs:

Area or object that has the approval process already attachedApproval objectChange in the approval process of the object or area
Project or template approvalProjectBecomes a single-use approval process and the status associated with it updates to match a similar status for the new group.
Task or template task approvalTaskBecomes a single-use approval process and the status associated with it updates to match a similar status for the new group.
Issue approvalIssueBecomes a single-use approval process and the status associated with it updates to match a similar status for the new group.
Tasks area in the Edit Project or Edit Template boxTask

The Task Default Approval Process field is reset to N/A

By default, no approval processes are associated with new tasks on the project

Queue Details section of a project or templateIssue

The Default Approval Process field is reset to N/A

By default, no approval processes are associated with new issues or requests on the project

Queue Topic section of a project or templateIssue

The Default Approval Process field is reset to N/A

By default, no approval processes are associated with new issues or requests on the project

Changing an approval process from group-level to system-level

When someone changes the Group option in a group-specific approval process to “All groups,” the approval process becomes system-wide and the following occurs:

Area or object where the approval process was attachedApproval objectChange in the approval process of the object or area
Project or template approvalProjectNo change
Task or template task approvalTaskNo change
Issue approvalIssueNo change
Tasks area in the Edit Project or Edit Template boxTaskNo change to the approval process but, by default, it is associated with new tasks on the project
Queue Details section of a project or templateIssueNo change to the approval process but, by default, it is associated with new issues or requests on the project
Queue Topic section of a project or templateIssueNo change to the approval process but, by default, it is associated with new issues or requests on the project

Changing an approval process from system-level to group-level

When someone changes the availability of a system-wide approval process from “All groups” to a specific group, the approval process becomes group-specific and the following occurs:

Area or object where the approval process was attachedApproval objectChange in the approval process of the object or area
Project, task, issue, template, or template task that belongs to the group of the approval processProject, task, or issueNo change
Tasks area in the Edit Project or Edit Template box for a project or template that belongs to the group of the approval processTaskNo change to the approval process but, by default, it is associated with new tasks on the project
Queue Details section for a project or template that belongs to the group of the approval processIssueNo change to the approval process but, by default, it is associated with new issues or requests on the project
Queue Topic section for a project or template that belongs to the group of the approval processIssueNo change to the approval process but, by default, it is associated with new issues or requests on the project
Project, task, issue, template, or template task that belongs to a group other than the group of the approval process

Projects

Tasks

Issues

Becomes a single-use approval process
Tasks area in the Edit Project or Edit Template box for a project or template that belongs to a group other than the group of the approval processTasks

The Task Default Approval Process field is reset to N/A.

By default, no approval processes are associated with new tasks on the project.

Queue Details section for a project or template that belongs to a group other than the group of the approval processIssues

The Default Approval field is reset to N/A.

By default, no approval processes are associated with new issues or requests on the project.

Queue Topic section for a project or template that belongs to a group other than the group of the approval processIssues

The Default Approval field is reset to N/A.

By default, no approval processes are associated with new issues or requests on the project.

Moving or copying a task or an issue to a project with a different group than that of the approval process

Moving or copying a task or an issue from a project to another might affect existing approval processes on the task or the issue depending on the groups of the two projects. The following table illustrates the scenarios that might exist:

Original task or issue approval processGroups of the two projectsChanges in the approval process after the task or issue is moved to another project
Single-use approval process associated with a system-wide statusProjects are in the same or different groupsNo change
Single-use approval process associated with a group-specific statusProjects are in different groupsThe approval remains a single-use approval process and the status associated with the approval updates to match a similar status for the new group.
System-wide approval processProjects are in the same or different groupsNo change
Group-specific approval processProjects are in the same groupNo change
Group-specific approval processProjects are in different groups and the groups have different group-specific statusesThe approval becomes a single-use approval process and the status associated with the approval updates to match a similar status for the new group.
Group-specific approval processProjects are in different groups and there is a status with the same key in the new group as the status associated with the approval process from the first groupNo change
Previous pageGlobal approval process settings
Next pageCreate a milestone path

Workfront


Learn: Automating Workflows with Workfront Fusion - Unique Use Cases in Action

Workfront

Tuesday, Mar 4, 6:00 PM UTC

Looking for creative ways to use Workfront Fusion to solve business challenges? Join Pan Shahbazian of Starbucks as she shares three unique use cases that can transform your workflows.

Register

The Perfect Blend: A New Era of Collaboration with AEM and Workfront

Adobe Customer Success Webinars

Wednesday, Apr 2, 5:00 PM UTC

Explore how Adobe Experience Manager and Workfront integrate to help teams move from ideation to delivery without the usual bottlenecks, ensuring content is organized, on-brand, and ready to go live faster.

Register

Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more

Register to learn something new

WORKFRONT

Join Adobe product experts in live events where you will learn Adobe Workfront best practices, tips and tricks, and hear about the latest product features and updates.

Register