M201 [DEFINITION GENERAL] Defining Business Process, Running on Workflow : Questetra

1. Drawing of Flow Chart: Design a flow of business by placing icons, and link them with arrows
2. Setting of Data Items: Define the [name] and the [type] of input items that are to be handed on , one by one
3. Setting of Permission: Set each data item to be read or to be input, in each step
4. Setting of Split: Set Splitting rule to each Split point
5. Enumerating Personnel to be Offered: Enumerating nominees who are the Persons to be Offered to operate each step (M209)

R2010 List of Task Icons (BPMN)

All the setting is done on the browser (Flash Player / constant connection is required)
There will be no session timeout due to non-operation (There is possibility of session termination due to the change in the communication condition)
Simultaneous editing by multiple people is not supported (Will be overwritten with the latest editing)
Assignment of Users or Role information are managed in the whole system (Cannot Set by individual App)
More than 500 samples of [Apps] have been published in the sample archive (extention : .qar）

a. Activate: To build a new Workflow system or to update version, click on the [Release developing Version] button
b. Suspend: To disable the Start new Process action, click on the [▼App] button, then select [Suspend]
c. Restart: To make a suspended Process Model to allow to Start new Process, click on the [▼App] button, then select [Restart]

A Process Model containing Definition Error cannot be Released
Version number of a Process Model will be given at each time of Releasing
You can leave version note when the Process Model is Released
Each Started Process continues to flow according to the “definition at the Starting”, even the version was updated during running
The option of terminating all the Processes in progress upon [Suspend] is also available

1. Modification on App settings: Update the Split setting or setting of underwriting candidate, etc.
2. Save and Release: Release the new version

Once you create a new application and release it, it will run as “version 1”
The setting modification after the initial release will be automatically saved as “version 2”. (It does not affect running App)
In order to update the App to “version 2”, “Release” version 2 again

a. Debug execution: Conduct [Debug execution] on Developing version of Process Model, by flowing an Issue to check its operation

You will be able to flow an Issue on the Developing version, even without [Releasing] it
You can select arbitrary [First Tasks] which is connected to [Start event]
It is also possible to operate all of the Steps by yourself (Option of “Allocate all Tasks to me”)
You can select a [Profile] If you are using the [Variables] in the Process Model Definition

a. Duplicate: [Copy] the previous version you want to go back, and Release it as another Process Model

Only the Definition information will be duplicated (Process data (Business record) will not be duplicated!)
If you need to take over the business data, you will need to edit and to update the current version manually

a. Delete: [Delete] the Process Model only when you want to delete all the definition information and business data in the Process Model

	50. Questetra Tips
	Apr 03, 2018	Reliable for Large-scale Organizational Change! Method for Realizing Automatic Release (Revised)
	50. Questetra Tips
	Mar 27, 2018	Reliable for Large-scale Organizational Change! Method for Realizing Automatic Release
	50. Questetra Tips
	Dec 05, 2017	Let's Create a Cool(?) Questionnaire Management System! (2)
	50. Questetra Tips
	Nov 28, 2017	Let's Create a Cool(?) Questionnaire Management System! (1)

Defining Business Process, Running on Workflow