...
Reference | Description | ||||||
|---|---|---|---|---|---|---|---|
| Information about the user who started the process instance. | ||||||
| Information about the starting time of the process instance. | ||||||
| Name of the process instance. | ||||||
| A description of the process instance that can be edited. | ||||||
| An instance can be archived by clicking this button. For further information, please see 'Archive process instances'. | ||||||
| By clicking this button, this instance can be used as a template. Both new process instances and templates can be created on the basis of the current process instance. Please find more information in the sections 'Create a template from an existing process instance' and Start a new process instance'. | ||||||
| Smartform locks can be removed. See Section Handling | ||||||
| By clicking this button, a process instance report and a efforts report can be generated. In this context, please regard chapter paragraph 'Reporting'. | ||||||
| If the process instance name or the description field is edited, the changes can be saved by clicking this button. |
...
Only users with the role process manager can view activities.
...
Reference | Description | ||||||
|---|---|---|---|---|---|---|---|
| The name of the activity. | ||||||
| This shows how many tasks the activity contains and how many have already been completed. | ||||||
| The description of an activity is displayed here. | ||||||
| The start time of the tasks is displayed here. | ||||||
| By clicking this button an activity, which is waiting for an event, can be signaled. |
...
Reference | Description | ||||||
|---|---|---|---|---|---|---|---|
| Name of the process instance. | ||||||
| Information about the user who started the process instance. | ||||||
| Information about the starting time of the task. | ||||||
| Information about the calculated end of the task. The calculated end is calculated from the start date of the task and the processing time of this task. Please refer to Critical Path Method (CPM) for further details on this topic. | ||||||
| The name of the task given in the process model. | ||||||
| Here, the description of the task is shown. The description is defined in the process model and cannot be edited. | ||||||
| By clicking on this button a query can be started. The current task is interrupted, so it doesn't appear in the task list of the user anymore. The “make a query” is assigned to another user. As soon as the “query” is done, the original task gets active again. Please regard the chapter 'make a query' for more information. | ||||||
| By clicking on this button an AdHoc task can be started. An AdHoc task is a task, which must be done in addition to the scheduled tasks. For more information, please regard the chapter 'Create AdHoc task'. | ||||||
| By clicking on the button Grab, the user can assign a task to himself/herself. If a task is assigned to the current user, this button is replaced by the button Throw. With this button, users can hand over tasks it if he/she cannot complete it. Please regard the chapters 'Throw tasks' and 'Grab tasks' for more information. | ||||||
| By clicking on this button a task will be finished. For more information please regard chapter 'Finish task'. | ||||||
| Here the number of attached documents and notes is displayed. By clicking on one of the fields the corresponding tab will be opened. For more information, please regard chapter 'Documents' and 'Notes'. | ||||||
| The assignment area is usually only visible for process managers or team-managers. However, this functionality can be made available globally for all users in one tenant. For more information, please regard the chapter 'Task assignment'. |
...
Documents
It is possible to attach documents to a process instance; for example, to display process-relevant information. These documents can be uploaded and then downloaded and viewed by those who are involved in the process. The layout of the documents tab is described in detail below.
...
The system offers the user the chance to summarize the potential accumulation of monetary or temporal efforts within a task. In the tab Efforts of a process instance, all recorded efforts are summarized for the entire process instance. Efforts can only be recorded for a task (see chapter 'Track efforts' for more information). In order to provide the process owner with an overview of all involved efforts, the cumulative efforts for all of the tasks are displayed. The layout of the tabs Effort and Efforts are described in detail below.
...
A process instance consists of a range of activities, which are executed in a specific order. A process instance only continues once an activity has been completed. An activity consists of one or more tasks that must all be completed before the activity can be considered as completed. For more information about processes and their structure in the chapter 'Definitions'. An activity can contain multiple tasks and is activated as soon as the process flow reaches the activity. For a user with the owner role, all activities are displayed in a list soon as an instance is selected.
...
The CPM Info will allow the user with the owner role to calculate CPM and to hand over buffer to the next activity. In order for calculating CPM the requirements must be meet.
...
Reference | Description | ||||||
|---|---|---|---|---|---|---|---|
| Checkbox to hand over spare time to the next activities should previous activities be finished ahead of the estimated time. | ||||||
| Calculate CPM computes the critical path for the current process instance. | ||||||
| Save will preserve made changes by the user. |
...