If you open the role editor, it contains an empty line already.
Start typing the name of the role your are seaching for in field Role. The field has an autocomplete function: As soon as you start inserting, a drop-down list is displayed containing all available roles that match your input.
Select the role you want to use.
In the next step you need to assign the rights that will be granted to the role owner.
Available options are:
Right
Description
Write
A user assigned to this role will be able to see and change the instance data for all process steps in the current lane.
Read
A user assigned to this role will be able to display the instance data for all process steps in the current lane.
This right is assigned by default.
List
A user assigned to this role will only be able to see the instances in the instance table for all process steps in the current lane.
You can continue to add further roles (or create new ones) as multiple roles can be assigned to one lane.
When you have finished, save your changes to apply them to the lane.
The number of roles assigned to a lane is displayed in the attributes panel.
You have to open the user management, to assign the new role to users.
Hover with your mouse over the Connectors tree node inthe service panel. Click the icon to create a new connector.
Alternatively, you can open the context menu of the Connectors folder and click Add OpenApi.
The Manage Connectors dialog is displayed.
Select a type of connector from the dropdown list.
Configure the connector in the Configuration section, e.g. OpenAPI connectors can be configured by simply importing a JSON or YAML description file.
Find more information about adapters and their related connector configuration on Adapters pp.
When you have selected an appropriate file, click Next.
The Next button is enabled only when you have selected a file.
If the selected file cannot be loaded, a corresponding error message is displayed in the dialog.
Additionally a (more detailed) toast message is displayed. The following error messages are possible:
Displayed Message
Possible Reason
Solution
The OpenAPI version 'x.y.z' is not supported. Versions 2.0.0, 3.0.0, 3.0.1, 3.0.2, and 3.0.3 are supported.
You have selected a file in a version that is not supported.
Select a file in a version that is supported.
The property 'swagger' or 'openapi' is missing.
The mentioned properties are missing from the file or are misspelled.
Check if the basic structure of the file is correct. For more detailed information about the basic structure of an OpenAPI file refer to OpenAPI Basic Structure.
The file cannot be loaded.
The selected file is corrupt.
Select a valid file.
The selected file has the wrong file type.
Select a file of a supported file type, e.g. a YAML description file.
After the selected file has been successfully imported, you can start the actual configuration of the connector.
When everything is configured to your needs, click Next to save the connector.
The connector, his types and interfaces, have been added to your service with the given configuration.
If you click icon the Field Configuration editor opens:
Use the editor to add and manage the content of your element:
Option
Description
Use the Add button to insert new rows.
Use icon Drag to change the order of the rows.
You can enter the options for this element as value pairs. When entering value pairs, always the first value (Value) is saved as key in the data container. The second value (Label) is used as notification to the user. The label is displayed in the form. Value pairs may also contain numbers, so that a user can chose a text option, but in the background a calculation is carried out.
Enter a Value for your element option.
It is not possible to assign the same value to different labels.
Enter a Label for your element option. The label is displayed in the form.
Use the scheduler if you want to define a pattern for your Timer Start Event, for example to start the model every monday, every hour etc.
Setting
Description
Default
Allow Parallel Executions
If checked, each time a scheduler pattern matches, the scheduler activity diagram is executed - even if another execution is already running. If not checked, the next execution cycle is suppressed if an execution diagram is already being run.
Checked
Year(s)
Insert a positive integer or a pattern.
*
Month(s)
Use numbers 1 to 12 or a pattern.
*
Weekdays(s)
Valid input:
Mon or Monday
Tue or Tuesday
Wed or Wednesday
Thur or Thursday
Fri or Friday
Sat or Saturday
Sun or Sunday
a pattern
*
Day(s)
Depending on the month, valid input are numbers from 1 to 31 or a pattern.
*
Hours(s)
Use 0 to 23 or a pattern.
*
Minute(s)
Use 0 to 59 or a pattern.
0
Seconds
Use 0 to 59 or a pattern.
0
Timer
Select the timer if you want to define a cycle for example to start the model after one week, after two hours etc.
Setting
Description
Default
Repeat Interval
Enter a valid time duration expression (see page Time Durations in the BRIDGE documentation for detailed information). This setting defines the time interval between two calls of the timer action.
-
Occurrences
Insert a positive integer to define the count of repetitions. If you want the timer to be endless, check Always (default).
Always
First Occurrence
Enter a valid time duration expression (see page Time Durations in the BRIDGE documentation for detailed information). This setting defines the wait interval after service start before the timer is executed for the first time.
0 seconds
Duration Expression Wizard
The settings Repeat Interval and First Occurrence contain the icon .
Click the icon to open a wizard that supports you to define the necessary duration expression.
Insert positive integers in the desired fields.
The result is shown below.
Click Save to close the wizard.
The duration expression is displayed in the corresponding field.
Once you are familiar with the notation of the duration expression, you can also insert it directly in the field.
For a role-based process model, you need at least one main lane.
You can then add sublanes.
To create sublanes, drag the next lane elements onto the header of the main lane element. Drop the new element on the border of an existing lane to position the new sublane.
To create a sublane within a sublane, you can drag the element onto the body of an existing lane.
To activate the lane element, click its border or icon/header. If the element is active, an indicator is displayed in the lower right corner and the border of the element is thicker.
Before Deletion:
After Deletion:
If you delete a lane element, it is erased from your work areaincluding all content! However, you can use restore the deletion by using Undo in the BPMN toolbar.