M414 PROCESS CONNECTION
Last updated Oct 05, 2017

Special Business Process for Aggregation on Business Data through Multiple Business Process

There are many cases that the Business Pprocess cannot be unified (standardized), despite leading to the same final deliverable, such as "personnel evaluation process in each division" or "invoicing process in each subsidiary". By operating a downstream Process which aggregates the final deliverable data, you are capable of aggregate management on this information. (Message Catch Event API)

M414-1-en


a. Liberalization of Upstream Flow
By not unifying deliberately, you will be able to entrust the improvement activities to each department
b. Control of Data Viewing Authority
It is also useful in cases you want to allow browsing all entry in Data Items only in their own division
  • Liberalization of the application route, and granting of Data Viewing Privileges could lead to the enhancement of the “self-governance of division”

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 App to the Released state after edit-save
  • Inform the Business App ID and Parameter names of the Business data to the designer of the calling side App
  • The designer of the calling side App 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 [App External Connectivity]

R3010 List of Authorization of System Privileges

R3020 Privilege of App Authorization

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 App ID (processModelInfoId) of the connection destination
c. Start Event ID of the Connection Destination
Specify the starting point (nodeNumber) of the App of the connection destination
d. The Security Key of the Connection Destination
Specify the security key of the App 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 helpful to use variables such as “$ {var [applicationRoot]}, as long as it is on the same Workflow platform

R2182 Error Notification of HTTP Start

R2210 Naming Convention for Data Receiving Parameter

M414-2-en

M414-3-en