Form Task Options Fields
These fields appear when you select a form task on the Configure Workflow step of the Workflow Configuration Wizard.
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.
Task Distribution
This field is only available if the Context Type value of the task is Portfolio. It determines whether the task runs against a portfolio planning period specified in the Context Object field or against objects that are included in the specified portfolio.
Context Object: The task runs against the portfolio planning period specified by the Context Type or Context Object field.
Selected Projects: The task becomes an iterative task, which means it is copied and repeated for all projects marked Selected or Forced In in the portfolio planning period specified by the Context Type or Context Object field.
Candidate Projects: The task becomes an iterative task, which means it is copied and repeated for all projects marked Unselected in the portfolio planning period specified by the Context Type or Context Object field.
All Scenarios: The task becomes an iterative task, which means it is copied and repeated for all scenarios in the portfolio planning period specified by the Context Type or Context Object field.
Scenarios for Review: The task becomes an iterative task, which means it is copied and repeated for all scenarios in the portfolio planning period specified by the Context Type or Context Object field.
Form
The portfolio or project form that the performer completes to complete the task.
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.
Completion Policy
This field is only available if the Performer field includes a group of more than one user. It determines how many performers from the selected user group must complete the task. This field has three possible values:
Any: Any assigned performer can complete the task to advance the workflow.
At Least Half: At least half of the assigned performers must complete the task to advance the workflow.
All: All assigned performers must complete the task to advance the workflow.
Confirm Task Completion
When set to Yes, the system prompts performers to verify that they have properly completed the task before it marks the task as complete.
When set to No, the system will not ask performers to confirm that they have properly completed the 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, November 19, 2024