A.Set up one approval task for each approver so that the project owner can decide who should approve

B.Use parallel approvers so that all approvers receive the approval task at the same time

C.Use conditions to customize the approval flow in the approval task

D.Use team member rules to assign users to the right project groups

A.Enable Template Upgrade so that existing contracts are upgraded when they are amended

B.Create templates in parallel so that settings can be compared during the configuration process

C.Export templates so that changes can be made more quickly using Microsoft Excel and a text editor

D.Create an initial template and receive business approval so that it can copied as the basis for additional templates

A.Standardized workflow is applied to all workspaces (Missed)

B.New header fields can be created

C.Template items can be deleted in projects

D.Workspace content can be re-used (Missed)

A.Place master agreements before sub-agreements (Missed)

B.Parent agreements must be loaded before the sub-agreement (Missed)

C.Hierarchical Type is an optional field on the legacy upload

D.A sub-agreement must be loaded in a separate zip file with no master agreements (Missed)

E.You can add a sub-agreement to a sub-agreement

A.To make all fields on a template unavailable for a specific user

B.To prevent users from creating their own master agreement document

C.To hide templates until usage is appropriate (Missed)

D.To make certain project groups appear based on field selections (Missed)