Most people think API’s are for software developers, but workflow systems are fundamentally for people who are in charge of the actual work. Questetra BPM Suite has message icons that can be placed on workflows and easily set-up, so users can decide to send/receive data to/from workflows.
Examples -- Send messages to:
Examples -- Receive messages from:
For detailed samples please see "Workflow-Sample.net".
Workflow-Sample.net
For example, a workflow from estimate to business contract is controlled by the sales department, but the following production portion is controlled by the production department. If the data that should be handed over between these two departments is established in advance, this can be automatically sent on the system.
Google Docs forms can be used as triggers that start workflows. For example, a sales department could have a web form for accepting prospective business deals, which flows to the sales team, who then make phone calls and send various materials.
For richer software development or advanced integration with enterprise systems, see the Software Development API page.
"To launch Workflow automatically" itself is a big business improvement.
In Questetra BPM Suite, in addition to start a business process manually, it automatic starts process using the " Process Model Connection API" (Conjunction Start). That is, a business process can be started from other process or from external program (external system).
When a lot of processes (business) come to flow actually, the discussion of improvement for how to flow business (the workflow itself) will be naturally activated. Let's rotate the improvement cycle appropriately along the improvement discussion such as modifying the input form note, or add a data item, or change the order and granularity, etc.
'Consigned Production Process' is started only on Commissioned Development project that reached to "Contract" through 'Negotiation Process'. It eliminates the need to re-enter the "project information", and also eliminates transcription errors.
Settings for Starting Process B from Process A
launches A Business Process that is set the value when there is input in form screen of Google Docs (SpreadSheet)such as 'Contact accept' or 'Campaign application'.
Setting Google Docs Form to Launch Business Process
BPMN: An international standard for defining process models (workflows). The standard maintains definitions of task and event icons. Today, workflows in the SOX Act are more often written in BPMN. Up until BPMN 1.2 the official name was Business Process Modeling Notation, but was changed to Business Process Model and Notation with the BPMN 2.0 upgrade (January 2011). [Click here for details]
API: Application program Interface or Application Programming Interface, for electronic communication for external sources. Original software using "Software Development APIs" can access data in Questetra BPM Suite with OAuth.
Message Start Event: An event that triggers a process to start. In BPMN this is indicated by a white envelope inside a single-line circle. In Questetra BPM Suite the data within a message sent by HTTP, etc., is turned into process data and starts a new flow. [Click here for details]
Message Catching Intermediate Event: An event that receives a message in the middle of a workflow. In BPMN this is indicated by a white envelope inside a double-line circle. In Questetra BPM Suite the data within a message sent by HTTP, etc., is internalized as the data of a certain process. [Click here for details]
Message Throwing Intermediate EventAn event that sends work information to an external system, in the middle of a workflow. In BPMN this is indicated by a black envelope inside a double-line circle. In Questetra BPM Suite, all or part of the workflow’s data is sent by HTTP or email (SMTP). [Click here for details]
workflow, business process management, saas, bpmn, software
