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 (the Receiver)
- 1. Design a Business Process
- Define the Business Processes using [Message Start Event]
- 2. Release the Business Processes
- Release the Business Processes in order to determine the starting point ID (nodeNumber), etc.
- (3. Make a note of the starting format)
- Display the format (API) to trigger the automatic start and write down its contents
- The automatic start parameter (start-up format) will be confirmed by putting the Process Model into a running state after saving the changes
- 3. is required when using "Z. More Info (HTTP)" on the caller side (Z. Additional information)
BPMN Icons: Message Start Event (HTTP)
3. Design the Connection Source (the Caller)
- a. Service Task (HTTP Request to Start Event)
- A Service Task to connect to a Start Event has been added to the modeler's automatic process palette
- b. Business data to be delivered
- Specify the values and Data Items to be sent as necessary
- The name of the Service Task is the App ID of the receiving Event, App Name, Node Number: Step Name.
- Process start-up will fail if the required settings for the Data Items to be delivered, or settings that do not satisfy the input check items are set.
R2182: Error Notification of HTTP Start
R2210: Naming Convention for Data Receiving Parameter
BPMN Icons: Service Task (HTTP Request to Start Event)
Z. More Info: Using Throwing Message Intermediate Event
- 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)
Comments
0 comments
Please sign in to leave a comment.