Skip to content

BPMN high-volume-batch: aggregate must be BPMN.ScriptTask to set policySatisfied (from #3217 review) #3229

Description

@nikhil-maryala

Context

From @rockymadden's #3217 review. high-volume-batch-guide.md authors aggregate as a bpmn:serviceTask (Shape table + the "What to bind" bullet: "apply the policy and set policySatisfied"). But policy_gate reads =vars.policySatisfied == false against a true default, and a bare bpmn:serviceTask carries no uipath:activity/uipath:mapping/uipath:output, so policySatisfied never changes and end_failed is unreachable at runtime.

Fix

aggregate should be a bpmn:scriptTask (BPMN.ScriptTask) — the one bundled type that computes and writes a variable (structural-bpmn.md:158-217; requiresDiscovery: false, so one deterministic registry get BPMN.ScriptTask). The Jint helper uipath.aggregate (structural-bpmn.md:164) is exactly what sums per-item results inside it.

  • Update the Shape table (row aggregate) and the "What to bind" bullet to say bpmn:scriptTask / BPMN.ScriptTask, linking structural-bpmn.md:158.
  • check_greenfield.py:57 already counts scriptTask as work, so no criteria change needed.

Acceptance

high-volume-batch's aggregate node can actually set policySatisfied, and the guide names BPMN.ScriptTask + the uipath.aggregate Jint helper correctly (no "doesn't exist" negation).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions