There are many cases where it is desirable to connect Business Apps to each other, such as a Quotation App to an Order Acceptance App, or a Shipping App to a Billing App. By connecting a [Service Task (Start Child Case)] and [Message Start Event (HTTP)] downstream Cases can be started automatically. (Message Catch Event APIs)
1. Situations that Start Another Case
- a. Dividing the Business Apps
Improve visibility and clarify responsibilities
- b. Subroutine
You can put general-purpose tasks such as translate, sign or claim on a common base (M413)
2. Design the Connection Destination (child: the Receiver)
- a. Start point
Set up a [Message Start Event (HTTP)] that serves as the starting point of the flow
- b. Data Items received from parent Case
Prepare Data Items to store information necessary for business operations received from the caller (parent Case)
- Data items received from the parent Case
- Set the edit permission to [Editable] in the properties of [Message Start Event (HTTP)]
- When the App is released, an icon [Service Task (Start Child Case)] will be automatically created in the same workflow platform to invoke this App
BPMN Icons: Message Start Event (HTTP)
3. Design the Connection Source (parent: the Caller)
- a. Calling point
Set up a [Service Task (Start Child Case)] for the App to be called as a child Case
- b. Business data to be passed
Specify values and Data Items to be sent to the child Case as necessary
- The [Service Task (Start Child Case)] is listed in the [Auto-Processing Task] palette on the App editor screen > [Connect with other workflow Apps] with the name "App ID App name Node number: Step name"
- Specify the data to be passed to the child Case in the [Values to be passed to the Child Case] tab
BPMN Icons: Service Task (Start Child Case)
Tutorial: Linking and Operating Multiple Workflow Apps – Splitting Apps Edition
Z. More Info: Using [Throwing Message Intermediate Event (HTTP)]
- a. Auto start URL of the destination
https://karasumi-shijo-000.questetra.net/System/Event/MessageStart/123/0/start.
- b. Security key of the connection destination
Specify the security key of the connection destination App.
- c. Business Data to be delivered
Specify the reception parameter name of the connection destination if necessary, and specify the value to be sent.
- It is possible to substitute the [Access URL] with "${var[applicationRoot]}System/Event/MessageStart/123/0/start" as long as it is on the same workflow platform
- Within the above URL
- 123: The App ID (processModelInfoId) of the connection destination
- 0: The Starting point (nodeNumber) of the connection destination App
BPMN Icons: Throwing Message Intermediate Event (HTTP)