M413 PROCESS CONNECTION
Last updated Dec 21, 2016

Setting: Calling Sub-process in the Middle of the Flow, Standing by the Result of It

There are many business operations that are called from other multiple operations. You should consider to isolate these Processes as Subroutine (Sub-process), such as a "Shipping Process" which is called from "Web Order Process" or "Fax order Process", or a "Translation Process" which is called from "Press Release Drafting" or "Website Updating". (Process Model Connecting APIs)

M413-1-en


a. Calling for Specialized Operation
It makes easier to incorporate requests for the experts, such as “Brand strategy unit” or ” Legal Department”
b. Decomposition of Direct Business
You can make jobs of such as “Document Translation” or “Icon designing” into the company-wide common platform

1. Publish the Starting Format
Publish the format (API) for automatic Starting to the related departments
  • The automatic Starting parameter (Starting Format) will be determined, by making the Process Model to the Released state after edit-save
  • Inform the Business Process ID and Parameter names of the Business data to the designer of the calling side Process Model
  • The designer of the calling side Process Model is also able to confirm the parameters at Send Parameter Setting in the property screen of [Throwing Message intermediate Event (HTTP)]
  • Users who are granted [System Administrator Privilege] are also able to confirm the parameters at [Process Model External Connectivity]

a. URL for Automatic Starting of the Connection Destination
https://karasumi-shijo-000.questetra.net/System/Event/MessageStart/start
b. Business Process ID of the Connection Destination
Specify the Process Model ID (processModelInfoId) of the connection destination
c. Start Event ID of the Connection Destination
Specify the starting point (nodeNumber) of the process model of the connection destination
d. The Security Key of the Connection Destination
Specify the security key of the Process Model of the connection destination
e. Business Data to be Passed
Specify “Receiving Parameter name” of the connection destination, if necessary, specify the value to send
  • It is possible to substitute with “$ {var [applicationRoot]} System / Event / MessageStart / start”, as long as it is on the same workflow platform
  • It is possible to substitute with “${var[key]}”, as long as it is on the same workflow platform

R2182 Error Notification of HTTP Start

R2210 Naming Convention for Data Receiving Parameter

M413-2-en

M413-3-en