Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

  • Configure the desired initiators and other responsible people persons 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 property 'Sharing allowed' in the object type the process is started the property 'Sharing allowed'for.
  • 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 group. It is also used by 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.

Delivered as project file:

View file
nameApproval-v2-13.bpmdefzip
height150

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 start form is opened as shown below. The following information has to be set:

  1. Approver: select the user who should approve the document.
  2. Read group: select an org-object (user or group), which can read the document after approval.
    This field can be filtered, so that only users or groups are suggested in respect to the corresponding checked box.
  3. Request: A short text for the approval request. This text is

...

  1. internationalized in respect to the

...

  1. user's 'Language' setting.

...

  1. Deadline: This deadline is set after process start. If this deadline is overdue, the approver will get an e-mail as a reminder. This deadline is part of the task element in the inbox list.
  2. The 'Should the process be monitored?' flag

...

  1. controls whether the activity 'Monitor process' should be present in the creator's inbox.
  2. After start, the process subject shows the title and description of the object used for start followed by the deadline.

Image RemovedImage Added

When the requester selects clicks 'OK', the 'Approve document' activity is sent to the approver's inbox, and the 'Monitor process' activity is sent to the requester.

...

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 write a question and select the desired user.

...

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 the transition condition to the 'AnswerRequest' acitivity.

...

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

VersionDateAuthorDescription
v2-1415th Feb 2019Martin BartonitzSome more additional scriptings
v2-1310th Jul 2018Martin BartonitzAdapted client-side scripts to version 4.x
v2-624th Aug 2017Martin Bartonitz

Fixed script problem on activity 'Answer request'