Here you can enable/disable automatic (partial) recalculation of process monitor cache (fig. 1).
Fig. 1. Process Monitor settings unit
To edit the settings, click . To finish editing, click Save (fig. 2).
Fig. 2. Dialog box for editing general settings of the Process Monitor.
Disnable auto recalculation of process monitor cache:
Yes – full recalculation is enabled, meaning that the queue of partial recalculation and full update of process monitor cache is done automatically. If you turn this option on, you will see the Plan the cache recalculation execution checkbox (fig. 3), where you can set up the periodicity of this operation;
No – partial recalculation is enabled and is done every 5 minutes. This is the default settings.
Fig. 3. Dialog box for editing Process Monitor settings with disabled automatic cache recalculation.
In the update settings, you can select the start date of full cache recalculation and its periodicity. You can limit the update by business days only according to your company’s business calendar.
Business Process Task settings
This block is for configuring business process module settings (fig. 4). These settings modify the operation of business processes in the system and are taken into account when there are locked users.
Fig. 4. Business Process Task settings
To edit the settings, click . The dialogue box for editing will open (fig. 5).
Fig. 5. Dialogue box for editing Business Process Task settings
Execute on behalf of the user responsible for the instance
Yes - the user, responsible for the instance (by default process initiator), will be the author of all the process tasks by default.
In this case, the user responsible has access to all the process tasks, receives notifications on the process tasks activities and answers the questions of the executors. Thus, the user responsible can monitor the process instance execution progress.
If the user responsible for the process instance is locked, but process tasks must be assigned to him or her, you have to manually select a new user to be responsible for the process instance before such tasks are assigned.
No - the user, responsible for the instance (by default initiator) will be the author of the first instance task. The author of each following task is the executor of the previous one.
In this case, the user responsible has access to the tasks in their swimlane; the task notifications will be sent to the tasks authors, instead of the user responsible. Many processes are modeled so that a user, after executing their task, has no concern with the following tasks. However, authors of such tasks receive notifications on actions with them, i.e. the users, who are not responsible for execution of the tasks.
With such settings, there are no users in the system, who could monitor the entire process. We recommend that you select Yes for the Execute on behalf of the user responsible for the instance switch.
If the user responsible for the process instance is locked, but process tasks must be assigned to him or her, these tasks will be assigned to the immediate superior of this user (the first user who is above in the organizational structure and not locked).
. To finish editing, click Save (fig. 2).
