The following simple process model covers the most useful functionalities with only three activities, and should inspire you to build your own models. Let's have a closer look at the details.
| Table of Contents |
|---|
Process model overview
The model is internationalized. EN and DE are supported.
After import, the user 'root' gets the start action 'Approve document' for each object type.
Changes needed:
- Configure the desired initiators and other responsible people for the process model.
- Set the desired preset user/group-field 'Reader' in the start form script
- To have sharing execute correctly after approval, set for the object type the process is started the property 'Sharing allowed'.
- The selected approver must have the edit right on this object instance.
Import this process model (below) and feel free to use it for your purposes.
In the 'approval' activity, the forwarding action code is read for sharing the object with the selected 'Reader'-group, and the transition condition uses it as well.)
Version 2-13 / importable by management studio version 4.x .
Note: It may be that the action labeling of activity 'Approval' got lost. If so, you have to wait for an update of enaio.
| View file | ||||
|---|---|---|---|---|
|
Process start
After calling 'Approve document', the requester selects an approver. This field is filtered so only eligible users are selectable.
Next the requester selects the group who will have permission to read the document after it has been approved.
Finally, the requester writes a short text for the approval request. This text is personalized in the language set in the user's 'Language' setting.
At least one deadline can be set. (open: set as process period via script).
Not shown in the screen shot: A 'Should the process be monitored?' flag, which controls whether the activity 'Monitor process' should be present in the creator's inbox.
After start, the process subject shows the title and description of the object used for start followed by the deadline.
When the requester selects 'OK', the 'Approve document' activity is sent to the approver's inbox, and the 'Monitor process' activity is sent to the requester.
You can make the following modifications:
- Configure the process initiators and people responsible
- Limit the available object types for the process start
- Configure the filter on the user/group fields 'Approver' and 'Read group (Readers)
- Configure the deadline showing first tomorrow or ...
Activity 'Monitor process' (optional)
If the process creator set the 'Monitor process' activity, the requester can monitor the progress of his request.
To Do: Can be removed when the processes view shows process parameters as well in the future.
Activity 'Approve document'
The approver can now review the document. If he needs help from another user, he can formulate a question and select the desired user.
The approver can change the reader group.
The approver can include
The forward action options are 'Ask for help', 'Approve' and 'Reject' (open: use this selected action for the transition condition and this history entry).
After the approver forwards the activity, an entry is written to the process history (open: to the document object as well), and an information is appended to the request text. In addition, if the document is approved, the read permission is set for the reader group.
Hint: the flag 'Ask for help' is no longer needed, because the action code is used for transition condition to the 'AnswerRequest' acitivity.
You can make the following modification:
- Configure the filter on the user/group fields 'helper' and 'Read group (Readers)'.
Activity 'Answer question'
The 'Helper' receives this activity, which includes the requester's question and additional information about the request. The helper can review the document, answer the question, and click 'Send Response' to send the task back to 'Approve document'.
After the task has been forwarded, an entry with the answer is written to the process history.
Activity 'Notice about approval'
This activity informs the requester about the approver's decision.
To Dos:
- During process start_, check whether the object type used has the property 'Sharing allowed' and throw a toast notification.
- Forward the activity 'Monitor process' to finish the complete process.
- Add an activity for noticing the members of the 'Reader'-group.
- If available, set the deadline as a period and configure an action for the case that the end of the period is reached.
Process model version history
| Version | Date | Author | Description |
|---|---|---|---|
| v2-13 | 10th Jul 2018 | Martin Bartonitz | Adapted client-side scripts to version 4.x |
| v2-6 | 24th Aug 2017 | Martin Bartonitz | Fixed script problem on activity 'Answer request' |