Start a process and follow the engine

User tasks work like Camunda 7. A manager from the managers group approves the request. Returning it for correction assigns it to the initiator, alice; after correction, it goes back for approval.

Two business rule tasks in sequence: Decision_1 selects c from inputs a and b. The decision is compiled into a chain of Go if statements.

A method, service task, call to testSubProcess and exclusive gateway based on amount. With amount = 1, the default branch runs a script and two parallel branches with a join. A string value makes the first step fail: after 10 attempts over several minutes, fix the variables and retry from instance history.

Three parallel service task branches. Each enqueues a separate task; handlers for different job types run concurrently. The join waits for all three.

A three-second intermediate timer and boundary events. Demo methods are stubs, so the process follows its main path. See the walkthrough for ways to trigger boundary events.

Sequential multi-instance: the notification method runs three times, each as a separate queued step. The review task repeats until approved, up to three rounds. The completion condition is =approved; loopCounter holds the round number.

A receive task waits for paymentReceived from an external payment system. The message finds the instance by its business key. Send it with the button on the right or POST /api/v1/messages.

Two AI tasks send a prompt containing request and write a text category into category and JSON urgency data into triage. A model refusal follows the ai_refusal boundary error. The demo uses a stub; implement engine.AIClient to connect your own model.