add workflow system event listener demo

[ivy-lgi]

I can also give you a live demo if you wish 😉

[github-actions]

Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 3441ba7. ± Comparison against base commit 828c402.

♻️ This comment has been updated with latest results.

[ivy-lgi]

This demo shows how workflow system events can trigger processes. For that, a ProcessStartEventBean has been implemented that can be used with a program start element (see WorkflowSystemEventListenerBean). The bean triggers the process whenever the configured event is detected.

In this example, the processes execute logic when

• a new task has been assigned (has activator)
• a task has been delegated (activator has changed)

Of course, any custom logic can be implemented to react to workflow system events.

[Copilot]

Pull request overview

Adds a new workflow demo that starts processes in response to workflow system events (task/case created/changed), including a reusable ProcessStartEventBean and a corresponding example process with test coverage.

Changes:

• Introduce WorkflowSystemEventListenerBean (a ProcessStartEventBean) that registers an ISystemEventListener for workflow system events and starts a process on matching events.
• Add a new demo process model + dataclass to showcase reacting to task created/changed events and executing follow-up logic.
• Add a new BPM test for the demo and adjust a few existing tests / CI Maven args.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
workflow/workflow-demos/src/ch/ivyteam/ivy/system/event/WorkflowSystemEventListenerBean.java	New start-event bean that registers/unregisters a workflow system event listener and starts a process with event parameters.
workflow/workflow-demos/processes/WorkflowSystemEvent/WorkflowSystemEventListeners.p.json	New demo process wiring program-starts to workflow events and scripts that filter/act on task IDs.
workflow/workflow-demos/dataclasses/WorkflowSystemEvent/WorkflowSystemEventListenersData.d.json	Data class for passing workflow system event parameters + collected task IDs through the demo process.
workflow/workflow-demos-test/src_test/test/bpm/TestWorkflowSystemEventListeners.java	New automated test asserting executions triggered by workflow system events.
workflow/workflow-demos-test/src_test/test/bpm/TestProcurementRequestUserTask.java	Formatting changes + adjust how end data is retrieved from executed task.
workflow/workflow-demos-test/src_test/test/bpm/TestProcurementRequest.java	Formatting changes + adjust how end data is retrieved from executed task.
workflow/workflow-demos-test/src_test/test/bpm/TestBusinessCaseDataWorkflow.java	Test assertion relaxed from strict element sequence to presence-based checks.
.github/workflows/ci.yml	Add Maven property to use latest engine minor version (tests still skipped in GitHub CI).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ivy-cst]

I can also give you a live demo if you wish 😉

Could you show it to us after the daily tomorrow? I think others are interested in this too.

[weissreto]

Looks good

[ivy-lgi]

@weissreto Regarding using compareAndSet in the "Activator has changed" logic as suggested in person, I don't think it really works. compareAndSet requires an expectedValue, where the new value is set if the current value is equal to the expectedValue.
However, in this case, I don't know and don't care what the previous value is. I want to set the value if it is different to the new value.

[weissreto]

@weissreto Regarding using compareAndSet in the "Activator has changed" logic as suggested in person, I don't think it really works. compareAndSet requires an expectedValue, where the new value is set if the current value is equal to the expectedValue. However, in this case, I don't know and don't care what the previous value is. I want to set the value if it is different to the new value.

As discussed on the desc
You could do something like this:

var existingValue = customField.getOrNull();
if (customField.compareAndSet(exsistingValue, newValue)) {
   in.taskIds.add(id);
}