M411: Auto-starting a "Billing Process" Triggered by a "Shipping Process"

 

There are many cases where it is desirable to connect Business Processes to each other, such as a Quotation Process to an Order Acceptance Process, or a Shipping Process to a Billing Process. By connecting a [Service Task (HTTP Request to Start Event)] or a  [Throwing Message Intermediate Event (HTTP)] and [Message Start Event (HTTP)] downstream Processes can be started automatically. (Message Catch Event APIs)

1. Overview of Cases that Start Another Process

a. Dividing the Business Process

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 process

Prepare Data Items to store information necessary for business operations received from the caller (parent process)

• Data items received from the parent process
  • Set the edit permission to [Editable] in the properties of [Message Start Event (HTTP)]
• When the App is released, a process icon [Service Task (Start Child Process)] 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 Process)] for the App to be called as a sub-process

b. Business data to be passed

Specify values and Data Items to be sent to the child process as necessary

• The [Service Task (Start Child Process)] 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: Process name"
• Specify the data to be passed to the sub-process (child process) in the [Values to be passed to the Child Process] tab

BPMN Icons: Service Task (Start Child Process)
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)

---

X. Business Apps

• Order Report Process
• Estimate Creation Flow
• Online Estimate Storage Flow
• Contract Approval Process