Variables and incidents

Every process instance created for the order-process.bpmn process model requires an orderValue so the XOR gateway evaluation will happen properly.

Let’s look at a case where orderValue is present and was set as a string, but our order-process.bpmn model required an integer to properly evaluate the orderValue and route the instance.

Linux

./bin/zbctl --insecure create instance order-process --variables '{"orderId": "1234", "orderValue":"99"}'

macOS

./bin/zbctl.darwin --insecure create instance order-process --variables '{"orderId": "1234", "orderValue":"99"}'

Windows

./bin/zbctl.exe --insecure create instance order-process --variables '{\"orderId\": \"1234\", \
"orderValue\": \"99\"}'

Advance an instance to an XOR gateway

To advance the instance to our XOR gateway, we’ll create a job worker to complete the Initiate Payment task:

Linux

./bin/zbctl --insecure create worker initiate-payment --handler cat

macOS

./bin/zbctl.darwin --insecure create worker initiate-payment --handler cat

Windows

./bin/zbctl.exe --insecure create worker initiate-payment --handler "findstr .*"

We’ll publish a message that will be correlated with the instance, so we can advance past the Payment Received intermediate message catch event:

Linux

./bin/zbctl --insecure publish message "payment-received" --correlationKey="1234"

macOS

./bin/zbctl.darwin --insecure publish message "payment-received" --correlationKey="1234"

Windows

./bin/zbctl.exe --insecure publish message "payment-received" --correlationKey="1234"

In the Operate interface, you should now observe the process instance has an incident, which means there’s a problem with process execution that must be fixed before the process instance can progress to the next step.

Diagnosing and resolving incidents

Operate provides tools for diagnosing and resolving incidents. Let’s go through incident diagnosis and resolution step by step.

When we inspect the process instance, we can see exactly what our incident is: Expected to evaluate condition 'orderValue>=100' successfully, but failed because: Cannot compare values of different types: STRING and INTEGER

To resolve this incident, we must edit the orderValue variable so it’s an integer. To do so, take the following steps:

1. Click on the edit icon next to the variable you’d like to edit.

2. Edit the variable by removing the quotation marks from the orderValue value.
3. Click the checkmark icon to save the change.

We were able to solve this particular problem by editing a variable, but it’s worth noting you can also add a variable if a variable is missing from a process instance altogether.

There’s one last step: initiating a “retry” of the process instance. There are two places on the process instance page where you can initiate a retry:

You should now see the incident has been resolved, and the process instance has progressed to the next step.

Complete a process instance

If you’d like to complete the process instance, create a worker for the Ship Without Insurance task:

Linux

./bin/zbctl --insecure create worker ship-without-insurance --handler cat

macOS

./bin/zbctl.darwin --insecure create worker ship-without-insurance --handler cat

Windows

./bin/zbctl.exe --insecure create worker ship-without-insurance --handler "findstr .*"

The completed process instance with the path taken: