A BAW process is launched from a case as a case activity of type "Process": in Case Builder (or Case Designer on BAW) add an activity to the case type, choose Implementation = Process and pick the BPD from an installed process app / toolkit snapshot; the activity's data mapping connects case properties to the process input and output variables. At run time the activity starts (manually from Case Client, automatically by a precondition, or repeatedly) and the process instance runs as the activity's implementation - it appears in the case's work list, and its completion completes the activity.
Other ways to start a BPD from the case world:
- Case rules / preconditions: an activity with the precondition "property X changed" starts the BPD when the condition becomes true.
- From a script or an integration inside the case (Case REST or Content Platform Engine event): call the Process REST API POST /rest/bpm/wle/v1/process?action=start&bpdId=...&snapshotId=...¶ms={...} or the v2 POST /bpm/processes?model=...&container=....
- Case start event from a document (document filed in a folder) combined with an activity of type Process - the classic "inbound document starts the process" pattern.
# start a BPD from anywhere with the Process REST API (case id passed as input so the process can call back)
POST /rest/bpm/wle/v1/process?action=start&bpdId=25.7f0d...&processAppId=2066.1a...&parts=header¶ms={"caseId":"{CASE-ID}","claimNumber":"CLM-42"}
BPMCSRFToken: <token>Prerequisites: Case Management enabled in the BAW installation (question 2902), the process app installed on the same Workflow server and exposed so that it is visible to Case Builder (the BPD's "Expose to" team must include the case workers), and the solution deployed with the process app as a dependency.
References