Feast your eyes on the new and improved Dirigent.io 3.0

Transparency

We have been working hard on providing you with the coolest and most useful edition of Dirigent.io so far, which now includes even more elements you can design your processes with, as well as other improvements designed to make your process management as easy as possible, so check out what the 3.0 version has in store for you.

Work Orders and Work Order tasks

Aside from some minor attribute improvements, Work Orders have gotten an upgrade in the form of External IDs. External IDs are numbers generated based on a user defined pattern, that are attributed to Work Orders created based on a certain Template. When creating a Template, users can now define the pattern, which determines the number of digits the External ID will contain, how often it will reset, and the format it will take.

Work Order tasks

Work Order tasks that were used only for changing the statuses of Work Orders in previous versions can now be used to create new Work Orders, and update existing ones. The update option allows users to add new atributes to prviously configured Work Orders as a part of their workflow, within the Dirigent.io Desginer.

The External and Sub process

The external process and sub process elements are both used to carry our repetitive tasks contained within the main process, but they function differently. The External process element resemples the Sub processes from previous versions of Dirigent.io.

The Sub Process element contains a process within the main process. Unlike the External proces, it cannot be used in a number of different processes, only in the process it is created in. When the main flow reaches the Sub Process element, it is started, carried out and completed before the main flow can continue.

The External Process element contains a process within the main process. Unlike the Sub process, it can be used in a number of different processes, regardless of the process it is created in. When the main flow reaches the External process element, it is started, carried out and completed before the main flow can continue. The External Proces is created within the main process, but users can select External processes created in different main processes.

Events

In addition to the Start and End events that are an essential part of every process, the Dirigent.io Designed now contains two more types of events: Intermediate and Boundary events.

Boundary events are catching events that are attached to a task. This means that while the task is running, the event is waiting for a certain type of trigger. Boundary events can have one of the following types: timer, message, signal and error, each of which performs an activity once they recieve their designated signal.

Intermediate events can be throwing and catching and are visually represented by a circle with smaller circle inside and a marker placed within the circle to indicate the type of the Intermediate event. They can be Signal events, which means that they either throw or catch defined signals, or Message events, which means that they catch messages with a specified name.

Tasks

Previously titled Inbox, the Task page is where all the assignments of a user are stored. They are now devided into "To Do" and "Done" segments, while the former is further split up into three sections. "My tasks" are tasks that have been assigned to a single user, the "Available" segment is comprised of tasks that have been assigned to a group a user is a member of, while the "All tasks" section contains both of these categories.

The Confluence element

The new addition to the Dirigent.io Designer palette – the Confluence element, allows users to create and update their spaces, pages and comments automatically, within their workflow.

In order to use it, users must first configure a Confluence connector in the Connectors section of the application. The configuration of the connector that allows users to access their Confluence accounts is similar to the way the JIRA connector is configured.

The Git element

Users now also have another element to incorporate into their workflows – the Git task. The Git task is used for connecting to a remote repository in order to perform git commands like pull, clone or checkout. It uses the Remote agent connector, so in order for it to perform defined commands, the Remote Agent connector must be configured correctly.

Minor improvents and bug fixes

As with every update, we have a couple of tweeks in sotre that are sure to make business process modeling and management simpler and easier for you.

The Applications page

The layout of the page of individual applications has changed so as to reflect the changes in the main and sub processes. The preview of the process now takes up much of the lower part of the screen, while the bottom part is devided by recent cases and External processes.

Adding users manually

The new version allows easier user management in that users can now be added manually, without invitation. Unlike the invite user option, where the user recieves an invitation to create an account, the manually added user gets an email that contains a generic password which they can change once they log in.

Notification management

Users can now control whether or not they recieve email notifications when they recieve a task. They can do this by going to their profile page and checking or unchecking the user task email notification box. The default option is for the notifications to be turned off, which means that users need to opt in if they wish to recieve the emails.

Process import and export changes

The new version allows users to download XML and JSON files of the previous cases of any give process. The import, however, is possible only for XML files.