Cimera supports workflow. This means that an Item can be assigned to a User or a Group indicating that activity is now required by them.
An Item is deemed to be a Workflow item if
| • | it has an Assignee field
This is configured by the Cimera Administrator by giving the Item Type the Assignee attribute (specifically FLD:O$CIASSIGNEE). This is achieved by making the Item Type inherit Inherit_Workflow_Item or Inherit_Workflow_Version (TYP:@I_WORKFLOW_ITEM or TYP:@I_WORKFLOW_VERSION) |
All Item Types that support workflow will have an Assignee attribute that contains the group / user that the Item is currently assigned to. The user must be a registered Cimera user to participate in workflow.
Assigning
A workflow item can be assigned to a group or a user in the context of a group.
A workflow item can NOT be assigned to a user.
For example
Problem PR-123 can be assigned to
the Development team, Development
or specifically to Dave in the Development team Development\Dave
but not to just Dave. Dave
Dave may be in multiple groups and this item is being assigned to him because he is a member of that team and not just because it's Dave
Similarly:
Testing
Testing\Tina
Analyst\Adam
are all valid Assignees. Tina or Adam are not
When an Item is assigned to a user then it will appear in their My Queue pane.
When an Item is assigned to a group (and not a user) then it will appear in the Group Queue pane for all users of that group.
The user can also select to see Items that are assigned to other users within the same group.
A Problem is created and is automatically assigned to the Problem Management group.
It now appears in the Group Queue for the users who are assigned to the Problem Management group.
A user within that group, and with the correct security privileges, can now assign it to themselves or to another user within the group.
It will now appear in that user's My Queue and no longer appear in the Group Queue (unless the Include those individually assigned check box is ticked)
