Process diagram
A process can have its own BPMN 2.0 drawing. In Proton, each task in the diagram is linked to the components that automate it, and the drawing is colored with the results of the latest runs: right in the business flow, you can see what passed, what failed and what has no automation yet.
The diagram is in the Process diagram section of the process details, in Processes > Process map.
Where the diagram comes from
- From REC: REC, by Atomic, records the process and sends the BPMN to Proton, with the system of each lane, the screen of each task and the recorded steps.
- From another tool: Import BPMN takes a BPMN 2.0 file exported from any modeler.
What the file needs
- A
.bpmnor.xmlextension, up to 10 MB. - BPMN 2.0 with at least one process.
- The diagram drawing (BPMN DI): export the file with the layout.
- No
DOCTYPE, which Proton rejects for security reasons.
What Proton reads
- The lanes, including lanes nested inside other lanes.
- The activities, which become the diagram tasks, including the ones inside subprocesses. Events, gateways and flows stay in the drawing only.
- The documentation of each activity, which shows up in the task panel.
The file is stored as it arrived, and Download .bpmn returns the XML of the version on the screen.
Versions
Each import creates a new version of the diagram, and the previous ones are kept.
- The Version selector shows each version with its source (Sent by REC, Imported or Restored) and the date.
- New version imports another file.
- On an old version, Go back to this version makes it the current one (saving a new version with the same drawing). You cannot link or unlink components on an old version.
The links between tasks and components carry over from one version to the next: they apply to the task with the same identifier. If a task changed its identifier but kept its name, it inherits the components of the previous one, and the import message says how many tasks inherited them.
The drawing and the colors
The drawing is view only: drag to move it and use Zoom in, Zoom out and Fit to screen. On a computer, Full screen opens the diagram in a larger window.
Above the drawing, a summary shows how many tasks have a component, how many are passing and how many are failing. Each task gets the color of its status:
| Status | When | Color |
|---|---|---|
| Failed | Some step of the task's components failed. | Red |
| No component | The task has no linked component. | Dashed gray border |
| Other status | No step passed or failed, and some step ended with another status (stopped, cancelled). | Orange |
| No run | The task has a component, but none of its steps ran. | Blue |
| Passed | Some step passed and none failed. | Green |
The calculation uses the latest run of each dataset of the automations of the process and its subprocesses (from any date) and looks at the steps that use the task's components. Only the automations you can see under the team rule are included.
The task panel
With no task selected, the side panel lists the ones that Need attention: the ones that failed and the ones with no component. Clicking a task (in the drawing or in the list) opens its panel:
- the name, the status and the type of the BPMN element;
- the Lane, the Subprocess and, when the diagram came from REC, the Recorded screen and the recorded steps;
- the Last run: how many steps of the components passed, failed or had another status, and when;
- the linked Components, in the format "component · system";
- the activity Documentation, as it came in the BPMN.
Link components
- Link a component searches the organization's components.
- On a task with no component, Proton suggests one, based on a name similar to the task's (favoring the lane's system). The suggestion only takes effect after Link.
- The component's X unlinks it.
- Each change is saved right away. A task has at most 20 components.
Linking components requires the permission to edit processes and the permission to view components.
Remove the diagram
The red Remove the diagram icon removes the diagram from the process, with all its versions and task links. The components and automations remain.
Permissions and mobile
- Viewing the diagram requires viewing processes; importing, restoring a version, linking components and removing the diagram require editing processes.
- On a phone, the diagram is view only: importing, linking and removing are done on a computer.