Assignments are a record of a temporary condition of an open work item within an executing flow. The condition requires a user or an external system to act on a work item for it to progress.
The phrase " perform an assignment" refers to a user's analysis, research, data input, and decisions that cause the assignment to be completed. (In certain situations, assignments can be processed completely or in part by a PRPC agent rather than by a person.)
Assignments are created by a flow operating on a work item, but assignments are not themselves part of the work item. The system saves data recording an assignment in instances of the Assign-Workbasket class, Assign-Worklist class, or other subclasses of the Assign- base class.
In a flow diagram, the shape in Process Modeler identifies an assignment, which references an activity with an Activity Type of
Assign. At runtime, assignments appear on a user's worklist, or on a workbasket's list, in decreasing order of urgency. The research, analysis, decision making, and data entry that a user does to complete the assignment is known as processing the assignment. After the assignment is complete, it disappears from the worklist.
When a flow execution reaches an assignment shape at runtime, the system performs the following processing:
Optionally, assignments may have an assignment status, with values such as
Next. This status is not related to the work item status, a different property in a different class.
Informally, the work that a user does to "perform" or complete an assignment is sometimes called a task. Standard version 5 reports in the Monitor Activity workspace summarize or analyze "task time" — how long the assignment was open. For example, the chart defined by the summary view rule Assign-Worklist.AgeByWorklistTask is called Timeliness by Task.
Standard properties recording user behavior and performance of assignments have "task" in the property name; for example pyPerformTaskTime.
Open topic with navigation