<img src="https://secure.frog9alea.com/152419.png" alt="" style="display:none;">

 

Release Notes Fall 2022

 

EMail banners Fall release-38 v2-38

The Fall 2022 release of Engage Process is planned for Wednesday 5 October 2022.

This release will automatically be active for all users of Engage Process.

Should you experience a problem in one of our applications on the release day (5 October), first try the following:

  • Press the following three buttons simultaneously: <Shift> + <Ctrl> + <Del>;
  • Then indicate if you want to delete only images and documents in the cache.

These steps will usually solve any problems. If you have tried these steps and you’re still experiencing a problem, you know you can reach us at support@engageprocess.com or, if you need immediate assistance, you can call us on +31 20 530 7280.

Enjoy discovering the new possibilities!

General

As you are accustomed from us, our Fall 2022 release contains many small(er) improvements, but this time several larger modifications and new functionalities have also been added. A list of the key points is provided below:

1. Findings

  • The Engage Process Modeler is an ideal instrument to use during process workshops. Such a workshop may be conducted for the benefit of mapping the current process but it can also be held to map a desired situation. Our experience has shown us that participants can already identify many improvements while mapping the current situation.

  • An optimal use of our Teamboard module, in turn, is as a process improvement board. The addition of “Findings” means an even closer collaboration between the Modeler and Teamboard is possible. Specifically, you can register findings from the Modeler and have a “ticket” directly created on a board within Teamboard. If the status of this ticket changes in Teamboard, you can then find that change in the process diagram in the Modeler. This allows you to focus more on clarifying and improving the process. While doing so, you can view the status of the implementation of the findings in the process diagram within the Modeler.

2. Sharing

Sharing diagrams (usually process diagrams) from the Modeler to the Viewer (app) has been expanded with extra options, specifically:

  • You can indicate an expiration date after which the shared diagram can no longer be viewed.
  • You can see an overview of shared diagrams as well as with whom they have been shared.
  • You can share a diagram with individuals who are not Engage Process users within your environment.
  • You can easily send Viewer links to people who are not users of Engage Process.

3. Approval module

  • Enterprise subscribers are able to use the Approval module, which allows you to indicate which processes must be approved and by whom before the process can or may be published. Now you can designate a group of users to be approvers of a process and also indicate the minimum number of persons within that group who must approve the process before it can be submitted for publication.

    For example: An HR process is offered for approval, and it must be approved by at least two employees of the HR department. There are five employees within the HR user group, but only two are sufficient for approval. The process will be offered for publication as soon as two of these five employees have given their approval.

4. Single Sign-On for customers with more than one domain

  • Within our Enterprise subscription, it is possible to activate Single Sign-On. In short, this means that users do not need to use a separate username and password to access the Engage Process Platform. This is directed from your Active Directory within your network. With the arrival of this new release, Single Sign-On can also be activated when you have multiple domains. And it doesn’t matter whether the domains are located on the same or different Azure Active Directory servers.

Modeler

  • Once a process has already been published, there is an option to automatically publish a process — after the process has been approved — without using the Publisher module.
  • Now a hyperlink can also be created in the field “Annotations”.
  • When sharing process diagrams and preparing the comments notification list, multiple e-mail addresses can now be specified instead of doing this one by one.
  • Within the Student subscription, process diagrams can be exported to Engage Process file formats, so these can be imported into the teacher environment.
  • The “Owner” field in process steps has been removed. Now that field only appears at the process level.

Viewer (App)

  • It is possible to create cross-reference reports about shared processes instead of only for the published processes.
  • Text which is displayed in the description, remarks and annotations can now be selected, copied and pasted into another application.

Publisher

  • Images used on overviews can now also be made transparent.
  • All shapes which can be used on an overview can have a fixed aspect ratio, so the shape is maintained when the size of the figure is enlarged or reduced. This is desirable, especially with circles.
  • Changing the order of diagrams and/or documents linked to a shape is now even easier with “drag and drop”.

Teamboard

  • Work items can now also be linked to shared processes in addition to published processes.
  • It is possible to display in a field a text which indicates what must be entered in that field. If not yet filled in, the field “Short description” can contain the following text: ‘Enter here a short description of the work activities to be carried out.’ This provides even more assistance and support to the user with respect to the correct use of the application.
  • The form that opens when you click on the pencil icon at a work item contains a table with an overview of any linked tasks. The columns of this table can now be adjusted.

Admin Center

  • Icons which are more inclusive — display more diversity — have been added to the icon library.
  • It was already possible to move table items from table A to table B whilst maintaining the references within the same table type, but now this is also possible between different table types. The table types must at least have the same properties, however.