Manual Decision Task Options Fields
Workflow Configuration > Create a Workflow Configuration > Workflow Configuration Wizard Fields > Manual Decision Options Fields
These options appear when you select a manual decision task on the Configure Workflow step of the Workflow Configuration Wizard. They control basic characteristics of the decision.
Context Type
The kind of object that the task runs against. Which values are available in this field varies by task type.
Budget: The task runs against budgets.
Budget Change: The task runs against budget changes.
Budget Transfer: The task runs against budget transfers.
Change Order: The task runs against contract change orders.
Changes: The task runs against contract changes.
Commitment: The task runs against contract commitments.
Contract: The task runs against contracts.
Idea: The task runs against ideas.
Portfolio: The task runs against the portfolio planning period specified in the Context Object field. You can also set Form tasks, Update Field tasks, and Sub-workflow tasks with a context type of Portfolio to run against objects that are included in the specified portfolio by setting the Task Distribution field to any value other than Context Object. With the Context Type field set to Portfolio and the Task Distribution field set to any value other than Context Object, the task becomes an iterative task, which means it is copied and repeated for all relevant objects in the specified portfolio.
Potential Change Order: The task runs against potential change orders for contracts.
Project: The task runs against projects.
Risk: The task runs against risks.
Same as sub-workflow (Sub-workflow tasks only): The task runs against the same object that the sub-workflow runs against.
Same as step: The task runs against the same object that the associated step runs against.
Submittal: The task runs against submittals.
Context Object
The specific project, project proposal, portfolio planning period, or scenario that the task runs against. If you do not specify a context object here, the context object is the object that the related step runs against.
Same as Step
For tasks that have a Context Type value of Budget but exist in workflows or steps that have a Context Type value of Project, this option specifies whether the task runs against the project that the step runs against.
Form (Optional)
Specifies a form that the performer can view or complete before answering the decision question.
Preassign Performer
Determines whether the system or the performer of the previous task chooses the performer of the task.
Yes: The system determines the task performer based on its other settings.
No: The performer of the previous task determines which user or user group performs this task. Which user or user group the performer of the previous task can choose is determined by the value of the Performers field. The Performer field can include users, user groups, or a combination of both. If it includes a user group, then the performer of the previous task may choose the entire group or an individual user from the group when specifying who should complete this task.
Performers
The user or users who perform the workflow task.
You can choose from three types of values in the Create Performer List dialog box:
Groups: Includes user groups created by your manager or administrator.
Users: Includes individual users.
User Fields: Includes users who are assigned to specific user fields in the object that the corresponding task runs against. For example, if the task runs against a commitment record, the User Fields option enables you to select the user assigned to the To Field in this record.
The All option enables you to choose any combination of user types.
Set as Workflow Initiator
When this option is selected, the user who initiated the workflow will automatically be assigned as the performer of the task.
Voting Type
In manual decisions assigned to user groups, this field specifies how performers' votes determine which path the workflow follows. If performers' votes make it impossible for the vote to meet the criteria of the selected voting type, then the system will assign the workflow manager an override task, which will require the workflow manager to decide which option the workflow proceeds with.
Any: As soon as any performer completes the manual decision task, the workflow proceeds with the option that the user chooses.
Plurality: The workflow follows the path associated with the option that receives the most votes. The system can determine this when all performers have voted or as soon as a tie is impossible and at least one performer has voted. If there is a tie between at least two options after all performers have voted, then the workflow manager is assigned an override task.
Majority: The workflow proceeds with the option that receives more than half of the votes as soon as more than half of the performers in the user group have chosen that option. If no option has more than half of the votes after all performers have voted, or if the system determines that it is impossible for any option to receive more than half of the votes, then the workflow manager is assigned an override task.
Unanimity: If all performers who are assigned the manual decision task select the same option, then the workflow proceeds with the path associated with that option. If any two performers select different options, then the workflow manager is immediately assigned an override task. The workflow does not proceed until all performers have voted for the same option or until the workflow manager completes the override task.
Notify
Use this field to specify which users who are not already involved in the workflow should be notified when the task is completed. You can include any combination of users, groups, or roles.
Include Workflow Initiator
When selected, the workflow initiator is notified when the task is completed, regardless of whether the workflow initiator is also selected in the Notify field.
Preassign Notification Recipient
Use this field to specify whether the system or the task performer chooses who is notified when the task is completed.
If set to Yes, the system determines who is notified based on workflow configuration settings.
If set to No, the task performer determines who is notified. Which users the task performer can choose is determined by the users selected in the Notify field.
Last Published Tuesday, May 21, 2024