Process Properties

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Process wizard > Model Process > Modeling for execution >

Process Properties

To display the Process Properties right click on the name of the process and select Properties. The following table will display:

 

Basic tab

 

Shape Properties2

 

PROPERTY

DESCRIPTION

Display Name

The name of the process to be displayed in the Work Portal. It can be changed through the Expert View.

Name

The name of the process. Spaces and special characters are not allowed. It cannot be changed.

Description

Include a description for the process. This description will be displayed when creating new cases.

 

Runtime tab

 

Shape Properties3

 

PROPERTY

DESCRIPTION

Help text

For documentation purposes, a Help text for the process.

Url Help

If you have documentation for your process, enter the URL.

Access type

Process: enables end users to create new case instances in the Work Portal.

Module: directly related to the Embedded sub-process. If a process is embedded it should have this access type. End users cannot create cases of these processes in the Work Portal.

Only sub-process: directly related to Reusable sub-processes. End users cannot create instances of these processes in the Work Portal.

Order

Defines the order in which processes will be displayed to create new cases in the Work Portal. Applies to each application individually.

Use Parent case number

This option enables the display of a single case number in the Work Portal for the parent process as well as its sub-process.  If this box is not checked, the sub-process will display a case number other than that of the parent process.

Enable alarms

Enables the configured alarms to send alarm notifications. If disabled, the configured alarms will not send emails.

Enable notifications

Enables the configured notifications to be sent. If disabled, the configured notifications will not send emails.

Category

Defines where your project is located according to your project's structure.

Global Form

It is associated form that is viewed when consulting a case that has been closed or when the user has no pending activities. For more information Global Form.

Summary Form

It is associated to the process and allows the user to view the progress information when clicking the Summary option of the pending cases. For more information Summary Form.

Estimated duration

Determines the maximum time that a Process can be active (unfinished) to consider that is still on time. It is defined in hours and minutes. Maximum values are:

o35791393 (Hours)

o59 (Minutes)

Lower Limit

Determines the estimated minimum run time of the Process. It is defined in hours and minutes. Maximum values are:

o35791393 (Hours)

o59 (Minutes)

Upper Limit

Determines the estimated maximum run time of the Process. It is defined in hours and minutes. Maximum values are:

o35791393 (Hours)

o59 (Minutes)

Version

Displays the version of the process.

State

State of the process (active/inactive). If it is checked, the process will be available to be used (if sub-process or module) and available for case creation (if it is a process). If inactive it will not be available to be used.

Mobile access

Indicates whether the element can be accessed from a mobile device or not

Risk signal

Allows you to customize the time frame in which an activity becomes "at risk" (marked with the yellow icon/semaphore in the Work Portal). The time set will define when a task turns yellow before expiring.

 

This property applies for all activities of the process and it is defined for each process particularly. It is not inherited by any sub-process (reusable nor embedded).

 

It does not consider the Working time schema. That is, if a Task expires at 8AM, and the Risk signal is set for 2 hours, it will turn yellow at 6AM.

 

The value entered in this property must be less than 24 hours. If no value is defined for this property, Bizagi will use 24 hours by default.

 

Risk signal value can only be modified in development environment, that is, if you need to update this value in production environment, you will need to perform a new deployment.