fix(workflow): use a DMN service task, not businessRuleTask (S-13, refs #14)
Some checks failed
CI / lint (pull_request) Successful in 1m15s
CI / build (pull_request) Successful in 58s
CI / unit (pull_request) Successful in 1m9s
CI / frontend (pull_request) Successful in 2m28s
CI / mutation (pull_request) Successful in 5m19s
CI / verify-stack (pull_request) Failing after 7m53s
Some checks failed
CI / lint (pull_request) Successful in 1m15s
CI / build (pull_request) Successful in 58s
CI / unit (pull_request) Successful in 1m9s
CI / frontend (pull_request) Successful in 2m28s
CI / mutation (pull_request) Successful in 5m19s
CI / verify-stack (pull_request) Failing after 7m53s
flowable-rest's businessRuleTask parse handler binds the legacy Drools/KIE implementation (NoClassDefFoundError: org.kie.api...AgendaFilter at deploy time), so registratie.bpmn failed to deploy and flowable-init exited 22. Flowable's supported inline-DMN construct is a serviceTask with flowable:type="dmn" — switch to it. The DMN cross-deploy via the process repository (previous commit) was fine; this was the BPMN parse. Docs/comments updated to match. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -270,7 +270,7 @@ services:
|
||||
until curl -sf -u rest-admin:test "$$base" >/dev/null 2>&1; do echo "waiting for flowable-rest..."; sleep 3; done
|
||||
# Deploy the diploma-eligibility DMN via the process repository: the flowable-rest image embeds
|
||||
# the DMN engine but does not expose the dmn-api app, so the process deployment cross-deploys the
|
||||
# .dmn resource to the DMN engine, where the registratie businessRuleTask resolves it by key
|
||||
# .dmn resource to the DMN engine, where the registratie DMN service task resolves it by key
|
||||
# (S-13, ADR-0016).
|
||||
if curl -s -u rest-admin:test "$$base?name=diploma-eligibility" | grep -q '"name":"diploma-eligibility"'; then
|
||||
echo "diploma-eligibility already deployed; skip"
|
||||
|
||||
@@ -51,7 +51,7 @@ services:
|
||||
until curl -sf -u rest-admin:test "$$base" >/dev/null 2>&1; do echo "waiting for flowable-rest..."; sleep 3; done
|
||||
# Deploy the diploma-eligibility DMN via the process repository: the flowable-rest image embeds
|
||||
# the DMN engine but does not expose the dmn-api app, so the process deployment cross-deploys the
|
||||
# .dmn resource to the DMN engine, where the registratie businessRuleTask resolves it by key
|
||||
# .dmn resource to the DMN engine, where the registratie DMN service task resolves it by key
|
||||
# (S-13, ADR-0016).
|
||||
if curl -s -u rest-admin:test "$$base?name=diploma-eligibility" | grep -q '"name":"diploma-eligibility"'; then
|
||||
echo "diploma-eligibility already deployed; skip"
|
||||
|
||||
@@ -159,7 +159,7 @@ done
|
||||
echo "OK — withdrawal cancelled the Beoordelen task; the registratie process ended (ingetrokken)"
|
||||
|
||||
# ── S-13: diploma-eligibility routing. A registration with a FOREIGN diploma must route through the
|
||||
# extra CBGVAdvies user task before Beoordelen (the DMN businessRuleTask sets route=CBGV_ADVIES and the
|
||||
# extra CBGVAdvies user task before Beoordelen (the DMN service task sets route=CBGV_ADVIES and the
|
||||
# gateway branches, ADR-0016). The domestic DIRECT path is already proven by the first registration
|
||||
# above, which parked straight at Beoordelen. ──────────────────────────────────────────────────────
|
||||
cbgv_query='{"processDefinitionKey":"registratie","taskDefinitionKey":"CBGVAdvies","includeProcessVariables":true}'
|
||||
|
||||
Reference in New Issue
Block a user