JOIN has an extensive workflow module. You can use it to define advanced routes along which addresses, documents or cases are handled. You can also add decision moments to the workflows. This affects a registration. Workflows are managed in JOIN Admin. If you do not have the workflow module, you can use the activities option.
In JOIN Admin, you will see three standard workflows in the Process Management folder: address, document and case workflows. Here you can add new workflows and modify existing workflows. In addition, User roles can be defined and checklists can be created.
Button | Description | Key combination |
---|---|---|
![]() |
Show full list | Alt A. |
![]() |
New | Alt N. |
![]() |
To copy | |
![]() |
Import workflow | Alt I. |
![]() |
Export workflow | Alt E. |
![]() |
New group for workflows | Alt G. |
![]() |
Save | Alt S. |
![]() |
Cancel | Alt C. |
![]() |
Delete workflow | Alt R. |
When creating a workflow, the steps below are included:
Note: when creating a workflow, do not forget to save it!
After creating a new workflow, you start designing the new workflow. There are several images on the left side of the Center. These are the different types of links that can be used within a workflow.
The different links that can be used within a workflow are:
1: starting point 2: handling 3: waiting point 4: assembly point 5: move to completed 6: computer action 7: checklist 8: subworkflow 9: manual decision 10: automatic decision 11: end point
Adding a link can be done in two ways:
The following applies to each link:
If a warning sign is displayed at the top right of the link, it means that this link has not yet been configured. If you move the mouse over this warning sign, you will see which action still needs to be taken.
The following sections explain how to provide the various links with the correct characteristics.
Switch on Start point
A starting point is automatically inserted when starting a new workflow. If you accidentally delete this, you can add the starting point again with this switch.
Switch: Practitioner
You have the following options:
Options | Description |
---|---|
User as practitioner | Select a user from the drop-down list. |
Practitioner as main registry | The practitioner is searched for in the registration to which the workflow in JOIN is linked. The practitioner is found in the first field in which the user table is displayed. |
User role as practitioner | Choose one of the roles as you have defined it in User Roles. |
Practitioner of previous action | Choose this option if you want the same practitioner as in the previous workflow step. |
User role from registration | The practitioner is searched for in the registration to which the workflow in JOIN is linked. The practitioner is looked up in the first field in which the user table is displayed and in this case is not a person but a user role. |
Options | Description |
---|---|
Alternately | The users take turns getting an action. |
Emptyest queue | The user with the smallest work queue gets the action |
Practitioner of previous action | Reuses the result of the previous distribution algorithm for this role. If the first action is placed on person A with ‘Take turns’, with ‘Previous practitioner’ the next action can also be placed on person A. |
Manual distribution | Everyone in the role gets an action. As soon as someone handles the action, the action disappears from the others’ list. |
Everyone in the role | Everyone in this user role will receive an individual promotion. This way, multiple actions can be set up at the same time and you don’t have to wait for each other. The handler of such an action cannot be changed from the work stock. |
Assign directly to the role | The action is assigned to a common work queue for all members of the user role, so that it is clear which work queue a team has. A member of the role can pick up and handle the action, but can still pass the action on to another team member. |
With a waiting point, ui ensures that the workflow is temporarily stopped. Examples of use cases:
Options | Gives |
---|---|
Until | Using the calendar, you can select a date to indicate until when the workflow should stop. |
Day / hour / min | Enter the number of days, hours and minutes. If necessary, indicate that it concerns working days. |
Till next | Select the day of the week on which the workflow should resume. |
Until day number | Indicates the day number. |
Till next …. Of the month | Here you can select a special day of the month, for example the second Saturday. |
Until date of registration | Here you can have the watch link look at a date in the registration. |
Switch: Rally point
You can merge several roads with a multi-point link. The workflow only continues after the collection point when all ‘incoming’ links have been processed. For example, you can determine that a number of tasks for the collection point are first handled in parallel and an action after the collection point is only started when all the preliminary work has been done. You can optionally indicate for this link what the status of this step in the workflow should be after collection.
Switch: Set to Completed
If the latest actions in a process are informative, then you can use the Set to Completed switch to finish the process earlier. Add this to the workflow.
The ‘date completed’ is then already entered before the last actions have been completed. The other steps are then informative.
Switch: Computer Action
With a Computer actions link you can have automated actions performed from the workflow. For example, it is possible to automatically create files, send mailings, create and change registrations. It is also possible to have actions carried out by an application that is linked to Decos.
Automatically merges registration information with a template and associates the result with a registration. For example, a confirmation of receipt can be created automatically. In a document workflow you can indicate whether the file should be created as a new registration. If you tick this option, you can then select the document book in which the new registration should be (automatically) registered. If you do not check this option, the file will be linked to the file tab of the document on which the workflow was started. You choose a template with which to merge the registration data. And finally, you can choose an address role that is relevant to the particular computer action.
By selecting this option an email can be sent automatically based on an email template. An email is then created and sent to recipients associated with the registration on which the workflow is based. For example, a confirmation of receipt can be sent automatically in the form of an e-mail.
In a document workflow you can indicate whether the HTML mailing should be created as a new registration. If you tick this option, you can then select the document book in which the new registration should be (automatically) registered. If you do not check this option, the mail will be linked to the file tab of the document on which the workflow was started. If you choose to link to an existing registration, you can also automatically add files to the mailing. To do so, place a check mark next to Attach files.
In the Display name field you can indicate which name the sender will see, for example Decos Customer Support. In the Reply to field you can enter the e-mail address that should be used to send any responses to, for example customersupport@decos.com. You can also indicate the subject that will be displayed in the final mailing. You choose an HTML template to be used in this action. And finally, you can indicate whether the mailing should be sent to an Address Role.
Change field value: With this standard action any field in a registration can be changed from the workflow. For example, a practitioner can be changed, the retention period, turnaround times or the expected end date.
Behind the Profile field, select the item profile containing the field value to be changed. Then choose the field that needs to be adjusted. If you want a macro to be applied, check this option. For example, with a macro it is possible to make the change take place based on a calculated value such as shifting an end date. After checking this option, enter the macro in the Field value field. If you do not choose a macro, enter a value from a table behind the field value.
By selecting this default action, the registration itself can be automated. The workflow can therefore create a registration in a chosen book and start a new workflow. Application options for this standard action include starting a new workflow from a document workflow with a notice of objection or to create another file from a file via a workflow. For example, complex cases can be divided or complaints that are expressed during a treatment can be handled as separate reports parallel to the main case.
Select the Book in which the registration should be created. You can create the registration in an Address book, a document book or a file book. Then choose the workflow to be started.
Regardless of the outcome of a standard action or availability of the other application, a computer action is always handled immediately.
Switch: Checklist
As a link, you can insert a checklist that allows a practitioner to get an overview of several actions on the screen in JOIN and to complete them in one go by placing check marks. Before you can use the switch Checklist, you must first have made a checklist. How to do this is described elsewhere in this manual.
Practitioner from the main registry || The practitioner is searched for in the registration to which the workflow in JOIN is linked. The practitioner is found in the first field in which the user table is displayed
Options | Description |
---|---|
User as practitioner | Select a user from the drop-down list |
User role as practitioner | Choose one of the roles as you have defined it in User Roles. |
Practitioner of previous action | Choose this option if you want the same practitioner as in the previous workflow step. |
User role from registration | The practitioner is searched for in the registration to which the workflow in JOIN is linked. The practitioner is looked up in the first field in which the user table is displayed and in this case is not a person but a user role. |
Options | Description |
---|---|
Alternately | The users take turns getting an action. |
Emptyest queue | The user with the smallest work queue gets the action. |
Practitioner of previous action | Reuses the result of the previous distribution algorithm for this role. If the first action is placed on person A with ‘Take turns’, with ‘Previous practitioner’ the next action can also be placed on person A. |
Manual distribution | Everyone in the role gets an action. As soon as someone handles the action, the action disappears from the others’ list. |
Everyone in the role | Everyone in this user role will receive an individual promotion. This way, multiple actions can be set up at the same time and you don’t have to wait for each other. The handler of such an action cannot be changed from the work stock. |
Assign directly to the role | The action is assigned to a common work queue for all members of the user role, so that it is clear which work queue a team has. A member of the role can pick up and handle the action, but can still pass the action on to another team member. |
Behind the Checklist field, you can select the desired checklist using a drop-down arrow.
Indicate what the status is once this checklist has been completed.
Choose an action description or action type (only one of these is possible).
If the main registration may be edited, place a check mark behind this field /
Indicate whether actions may be forwarded.
You can then indicate the term within which the action must be completed. You can also indicate that only working days are counted.
When you have entered all the information, click in the Center to continue building the workflow.
Switch: Subworkflow
You can add a subworkflow to a workflow, which will start a new process depending on a chosen decision.
You can enter these details on the right side of the screen.
Switch: Manual decision
A manual decision is made by a user (can also be divided by user role) on the basis of values from a table defined in Decos. The purpose of this step is to indicate the status of the step in the workflow when it has been completed, for example Completed, On order, Received.
In the field behind Attendant type you can make the following choice:
Click on the button behind Clinician. A screen appears where you can select a Clinician. You have the following options:
Options | Description |
---|---|
Practitioner from the main registry | The practitioner is searched for in the registration to which the workflow in JOIN is linked. The practitioner is found in the first field in which the user table is displayed |
User role as practitioner | Choose one of the roles as you have defined it in User Roles. |
Practitioner of previous action | Choose this option if you want the same practitioner as in the previous workflow step. |
User role from registration | The practitioner is searched for in the registration to which the workflow in JOIN is linked. The practitioner is looked up in the first field in which the user table is displayed and in this case is not a person but a user role. |
Options | Description |
---|---|
Alternately | The users take turns getting an action. |
Emptyest queue | The user with the smallest work queue gets the action. |
Practitioner of previous action | Reuses the result of the previous distribution algorithm for this role. If the first action is placed on person A with ‘Take turns’, with ‘Previous practitioner’ the next action can also be placed on person A. |
Manual distribution | Everyone in the role gets an action. As soon as someone handles the action, the action disappears from the others’ list. |
Everyone in the role | Everyone in the role gets an action. As soon as someone handles the action, the action disappears from the others’ list. |
Assign directly to the role | The action is assigned to a common work queue for all members of the user role, so that it is clear which work queue a team has. A member of the role can pick up and handle the action, but can still pass the action on to another team member. |
File: Icon Automatic Decision.png
An automatic decision is made by JOIN on the basis of conditions entered by you for field values of the document, file or address to which this workflow is linked.
File: Automatic Decision.png
File: Conditions.png
Note: if you selected ‘Similar’ as the comparison type in step 6, you can use the percent sign (%) as ‘wildcard’. ‘Place’ resembles ‘Amst%’ means that both Amsterdam and Amstelveen, as visiting residence, return the condition as ‘true’.
Switch: End point
An endpoint link indicates that the workflow has been completed in its entirety. An end point cannot be set further. You place an endpoint in the workflow by dragging the endpoint icon into the design sheet. There can be multiple endpoints in a workflow.
Connecting with links in the workflow
Click on a link where the connection should start
File: Connect With Links in the Workflow.png
Delete connections
You can remove connections between links in two ways:
Delete all connections to one object
Delete specific connection
Click on the link you want to change. The screen in which you have entered the details of this link appears on the right. You can enter the new values. Changing a decision link invalidates the connections leading to that decision.
You can also copy links. For example, to create a second treatment link with the same action code and lead time, but with a different practitioner.
Remove links
Export and import workflow
The export function is useful if you want to move a workflow from a test to a production environment. Even if you want to make a drastic change to a workflow that is already in use, it is recommended that you make a backup.
To export a workflow, proceed as follows:
The Export Workflow window appears.
To import a workflow, proceed as follows:
If you want to give Administrator level administrative rights to a workflow, you can indicate this on the Administrator levels tab. Two hyperlinks are visible on the tab: Linked administrator levels and Available administrator levels. Behind these hyperlinks is a number in brackets, which indicates how many levels are already linked and therefore have management rights and how many levels in total are available but do not yet have management rights. By clicking on a hyperlink, or by clicking on the arrow icon in front of the link, all Administrator levels from the relevant category are visible.
To link administrator levels:
To unlink an Administrator level:
You can also establish a link by dragging an available administrator level to the linked levels. And by dragging a linked level to the available levels, you will unlink it.
The list of available workflows may be very long. To keep it clear, you can organize it in groups.
Next, you will group workflows by dragging:
User roles are roles of groups of users that you can assign an action as a group in the workflow module.
Toolbar for user roles
Button | Description | Key combination |
---|---|---|
Show full list | Alt A. | |
New | Alt N. | |
New group for user roles | Alt G. | |
Save | Alt S. | |
Cancel | Alt C. | |
Delete user role | Alt R. |
File: New User Roles.png
To unlink a User:
Search for a User
The list of available user roles may be very long. To keep it clear, you can organize it in groups.
Next, you will group user roles by dragging:
Button | Description | Key combination |
---|---|---|
Show full list | Alt A. | |
New | Alt N. | |
New group for checklists | Alt G. | |
Save | Alt S. | |
Cancel | Alt C. | |
Delete checklist | Alt R. |
Making a checklist
Making a checklist is done as follows:
File: 1.png
File: 2.png
File: 3.png
File: 4.png
File: 5.png