M318: Controlling External Access to the [Message Catch Event API]

 

Questetra provides a [Message Catch Event API] that can Start a Workflow automatically and APIs that are capable of controlling User and Work resources. The [Message Catch Event API] is a mechanism that publishes a unique location (URL) each time an application designer releases an App that contains an Event for catching external requests. The system administrator should regularly check if unnecessary APIs have been published or not.

1. Overview of Questetra's [Message Catch Event API]

a. Message Start Event (HTTP)

 

By Receiving HTTP requests a new Issue will start automatically

b. Receive Task (HTTP)

 

Add data to the Issue in progress

c. Message Start Event (Form)

 

By posting to a Web Form a new Issue will start automatically

d. Message Start Event (Email)

 

By receiving an Email a new Issue will start automatically

System Settings – App External Connectivity

• The [Message Catch Event API] is set up in the Business Process definition (App)
• It is also effective when connecting Apps to each other (API for Making Process Connection: M411 - M414)
• Users with [System Administrator] authorization can comprehensively browse API open states of all the Business Process definitions
• Those Users can also comprehensively browse the [Throwing Message Intermediate Event (HTTP)] which transmits HTTP requests to an external server

2. Close Unnecessary APIs

a. Suspend New Start

[Suspend] Apps which are publishing an API

b. Delete Event Icon

After deleting the definition part of the opening API, release the App as a new version

• Even when you suspend an App and block a new Start it is possible to maintain ongoing Issues
• Even when modifying a definition and releasing an App as a new version the ongoing Issues will progress according to the old version
• To Modify Business a Process definition [App Administrator] authorization is required (M302)

---

X. Tutorial

• Starting a Process from Outside of Questetra BPM Suite