This article describes the necessary configuration steps to connect Camunda and i-doit.
Note: The processNow addon is currently only available as a bundle with the i-doit OPEN. You will find it in the download section. For processNow projects with i-doit PRO please contact us directly.
Running Camunda Server and reachable Webservice (download Camunda 7 tomcat edition from https://camunda.com/).
Setup processNow in i-doit
Install i-doit addon or use i-doit open edition with bundled processNow.
Login to i-doit and go to administration, select System settings and select Tenantsettings.
Go to “processNow” and setup the URL of your Camunda Server.
Attention: no trailing slash at the end – only fill in the hostname followed by the port (default: 8080).
Hint: The default Camunda installation comes without ssl encryption – so the URL starts with http (without s)!
How does processNow work/integrate?
After installing the processNow addon (ur using the i-doit open version with bundled processNow) a new Object Type “processNow Flow” appears in Group “Other”.
A “processNow Flow” record describes and holds some meta information about the (Camunda) Process/Workflow – called “processNow Flow” – and where this workflow can be started.
This means it can be configured which processNow Flows are valid for which Object Types (e.g. “Reboot Server” is allowed for all Server and Virtual Server CIs) or for which single CIs using static CI Groups.
If you are using i-doit PRO you can also use reports (dynamic CI Groups) to define the affected CIs where the specific processNow Flow can be started (don’t forget to setup the periodical cronjob using the i-doit console to periodically fill the groups).
So first start creating a new processNow Flow record with a Title.
This Title is used in the User’s dialog to start a new processNow Flow.
The processNow Flow definition
In the processNow Flow record (see group Other) a processNow Flow (Camunda Process/Workflow) has to be created (see above “How does processNow work/integrate).
The processNow definition defines the Camunda Process ID which has to be started.
This Workflow-Key/Process-ID must exactly match (case sensitive! Don’t use special characters or spaces!) with the Process ID used in BPMN diagram.
In field valid for object types the target Object Types can be defined.
So if Blade Server, Server, Virtual Server is defined (like in this example) this processNow Flow “Reboot Server” will appear in all CIs of type Blade Server, Server and Virtual Server.
Another option is to Setup specific CIs instead using a Object Type.
Specific CIs can be selected in “Object Group” using a static group and the Add/Remove Button..
Now this processNow Flow (in our example “Reboot Server”) is available in the “Smart Building Control Terminal” Client-CI.
The processNow Flow Camunda Process Auto-Discover
There is a feature implemented, to automatically discover all
If you open the processNow dialog from any CI the addon performs a synchronization between all deployed Camunda processes and the processNow Flow records.
So it’s very easy to start – just model a BPMN diagram, deploy it to the Camunda server and hit the “processNow” button.
After a few seconds the synchronization is finished.
Switch to group “Other” and click on “processNow Flow” and all deployed Camunda processes should appear in this list.
Now you can setup the valid Object Types and/or specific CIs for every processNow Flow.
Process Variables and Value replacement
The i-doit processNow Addon checks all “Generated Task Forms” Form fields defined in the BPMN diagram and show these fields as input for the user.
So the Form fields ID is used as name for the input variable and the Default value is used as prefilled default value for the input.
There are some special placeholders which are automatically replaced by the processNow addon:
Uses the CIs hostname defined in primary “Host address”
Uses the CIs hosts FQDN (full qualified domain name) defined in primary “Host address”
The CIs objid
The CIs objtypeid
The CIs title
The CIs sysid
© 2022 processNow