Cloud BPM v11.6 Supports Webhook Start

Event-notification of cloud era tightens service collaboration

PR-en-v116-webhook-start-20180312-1.pdf

Kyoto, Japan – March 12th, 2018 – Questetra, Inc., the global SaaS provider of Business Process Management (BPM), today announced that they have published the new version 11.6 of the Cloud-based Workflow product “Questetra BPM Suite” on Mar. 12th, 2018. This new version allows setting a Process to be triggered by Webhook. (Webhook receiving feature)

Even a Workflow system for improving productivity will become meaningless unless “Request” or “Registration” of the most upstream Step is made. The cloud-based Workflow, “Questetra BPM Suite”, has been corresponding to such as 1) Workflow start by a user in the system, 2) Automatic start triggered by “incoming email” from outside, 3) Automatic start triggered by an entry in a published Web form, 4) Automatic start triggered by “reception of standard HTTP request.

Since the new version 11.6, it becomes possible to automatically start the Workflow with the reception of “Webhook between servers” as a trigger. Specifically, it will be able to receive Webhook from “kintone”, a cloud database service, and “PayPal”, a payment service. With this feature, it becomes possible a collaboration, for example, which “Commodity registration flow” to the EC site is Started by adding products to “Product master” (kintone).

Questetra BPM Suite

Cloud-based Workflow “Questetra BPM Suite” is a business platform for realizing environments of paper-less and remote-working.

Business issues are controlled according to Business Flow Diagram. When a process reaches human task, the user will be asked to input. Also, when an issue reaches to automated Step, the predetermined processing (server-side processing) such as “Generate PDF” and “Save to cloud storage” is performed automatically. (BPM: Business Process Management)

You can apply it to various business operations such as “Approval request flow”, “Document translation flow”, “Quality check process”, “Invoice issuance process”. Process owner of each Business Process can practice “improvement of Business Process” little by little in daily work. (Examples of Business Flow Diagram: http://en.workflow-sample.net/ )

Catching Message Event API

Regarding Start Event and Catching Intermediated Event/Receive Task, a data receiving method that “To store the whole message body in a Data Item” becomes available in addition to “Storing values into respective Data Items as specified by parameter”. It is also possible to specify “Content-type” of the HTTP request to receive.

Message Start Event (HTTP): Start a Process upon arrival of an HTTP request at certain URL (Parameter)
Message Start Event (Webhook): Start a Process upon arrival of an HTTP request at certain URL (Message body)
Catching Message Intermediate Event (HTTP): Stand by for arrival of an HTTP request at certain URL (Parameter)
Catching Message Intermediate Event (Webhook): Stand by for arrival of an HTTP request at certain URL (Message body)

Setting of Webhook

Other Improvements

Process Details screen for Smartphones

Delegate/Return and Terminate/Delete become available on Smartphones. Also, a URL string entered in String type Data Item is automatically displayed as a hyperlink on a Process details screen.

Logging feature in Script Task

Regarding [Script Task] and [Service Task (Add-on)], it becomes capable of outputting logs to processing record using log output method. Also, error contents will be recorded automatically to processing log when an error occurs.