Quantcast
Channel: Cloud Workflow QUESTETRA BPM SUITE » Questetra Blog
Viewing all articles
Browse latest Browse all 37

Ver.10.4 Operation Test Becomes Easier!

$
0
0

 

How do you carry out operational checks when you newly created or modified a Process Model?

 

In the article in March 2015, I introduced the way of “How to duplicate a Process Model and check its operation”.

However, it was a bit cumbersome and had some challenges as follows.

  • You need to create a new Process Model only for operational check.
  • You need to take the steps that “Editing the Process Model in operation” ⇒ “Newly creating a Process Model for testing”.
  • You need to change the setting of the Operators if you tried to test by yourself alone.
  • You need to edit such as email destination or the access URL of APIs, as needed.
  • Process for testing will be remaining on (unless you remove it).

 

I am going to introduce to you the “Debug Process execution”, a new feature of ver. 10.4 Using this feature those problems above will be solved! You will be able to conduct Operational checks on Process Models easier.

What kind of feature is it?

It is a feature of “Debug execution” to perform testing / operational check.

 

Until now, you needed to Start a Process newly, after [Releasing] the Process Model to check the operation of modified contents. Using “Debug process execution”, you will be able to Start a Process for Testing (debugging) without [Releasing] the Model.

Who use? Where to Start?

“Debug process execution” is a feature for Workflow Designer. The menu is prepared on the Process Model Detail screen. Thus, this feature is available only for the Users who have [Process Model Editing authorization] on the target Process Model.

 

Please operate it from the menu on the Process Model Detail screen as in the figure.

[▼Version X(Developing)] > [Debug process execution]

v1040-debug-start

Options of Execution

There are some Options for execution provided in [Debug execution]. Specially, the option of “Allocate all Tasks to me” is very useful for the operational check on a Process Model in developing.

v1040-debug-option

First Task

Option for selecting the point of Starting the Process. [Human Tasks] which have been connected to normal [Start Event] are displayed as candidates.

  • In the [Debug execution], it is possible to start a Process, regardless of the Operator setting of the swimlane in which the first Task are located. The User who manipulates [Debug execution] will become the [Process Start User].
  • [Message Start Event] and [Timer start event] can not be selected as the starting point. (Ver.10.4)

Profile

In the case where *[Variables] is used in the Process Model definition, select a profile for Debug execution.
(*[Preference]>[Variables])

Utilizing [Preference], you will be able to switch, such as “Email destination” or “Access URL to send HTTP Request” of [Throwing Message Intermediate Event], in accordance with the profiles. Use this function in cases you want to send mail to different destinations from actual operation during test running.

v1040-debug-profile

Allocate all Tasks to me

Select [Operators] who handle Tasks. When this option is checked, all the Tasks will be allocated to yourself (who manipulates this procedure).

  • Checked: Not only the first Task, but also all the Tasks are to be handled by the person him or herself.
  • Unchecked: The person him or herself Starts a process and become the Operator of the first Task. After then, it follows the definition of the Process Model.

Management of the Process which have Started as Debug Execution

The Process which has Started as [Debug Execution] will appear on [My Tasks], etc. of Operator of each Step as well as normal Processes. The Issue will proceed according to the Process Model Definition and Debug execution options, and to be handled. Also, it will appear in the search results, if matches the conditions.

 

The difference between normal Processes are as below.

Indication

“Process in Debug execution” is obvious with its icon on the screens of such as Task Operating, a list of Processes, or Process Details.

v1040-debug-list

v1040-debug-process-detail

Automatically deletes

The Process which has Started as [Debug Execution] will be deleted automatically along one of the following actions.

  • Edit and Save the Process Model
  • [Release] the new version of the Process Model
Upon Debug execution, new numbers will be assigned to the [Process sequential number] and [Process ID]. When the debugging Process is deleted automatically, these numbers will become missing number (skipped number). (Noted that regarding the [Process sequential number], it is also possible to manage at;, [Process Model Detail]>[▼Process Model]>[Edit Process Sequence].)

 

 

By utilizing [Debug execution of Process], you will be able to change your Business Process more easily than ever before. Please make use of [Debug execution] feature upon modifying and improving the Business Processes, in order to immediately correspond the change of business rules or business performance.

 


◆ Related information

◆ Related manuals

 


Viewing all articles
Browse latest Browse all 37

Trending Articles