The project contains all the components required to trigger a boundary message event using REST calls
A serial approval pipeline process with two-levels. The tasks approved by first-level approver should route to task-list of second-level approver (Manager). The first-level approver should also have the capability to revert/recall the submitted tasks. Thus recalled tasks should be closed/moved out from second-level approver's (Manager) task-list and requeued back to first-level approver's inbox, without any loss of data.
- Alfresco Process Services (powered by Activiti) (Version 1.9 and above) - If you don't have it already, you can download a 30 day trial from Alfresco Process Services (APS).Instructions & help available at Activiti Docs, Alfresco BPM Community
- Import the Save-Face-BME.zip app available in this project into Activiti.
- The process flow.
- The process configuration.
- The boundary message event.
- The message event defenition.
- Publish/Deploy the App.
-
Use POSTMAN to make REST calls and trigger the Boundary Message Events.
TIP: Quickly import REST Calls from POSTMAN Collection.
-
As the first step, REST GET call should be to get the Execution ID of the targeted Boundary Message Event.
http://<hostname>:<port>/activiti-app/api/runtime/executions?tenantId=<tenantId>&processInstanceId=<instanceID>
The configuration is shown below. If necessary, the value of Execution ID can be cross-verified by querying the DB.
- As the second step, REST PUT call should send trigger for Boundary Message Event.
http://<hostname>:<port>/activiti-app/api/runtime/executions/<execution-id-of-boundar-message-event>?tenantId=<tenantId>
The header of PUT call is as follows:
Authorization = Basic xxxxxxxxxxxxxxx
cache-control = no-cache
content-type = application/json
The body of the PUT call is as follows:
{
"action":"messageEventReceived",
"messageName":"saveFaceMessage"
}