Step properties

Step properties  are set in the screen below. This screen appears when you press button "New step" in the Map designer screen or button "Step properties" on the same screen after selecting a step by mouse clicking on it. Both buttons are in the upper toolbar of the Map designer screen.

System name - unique name used for system needs is assigned automatically but can be changed by the developer

Name
- text that the end user will see inside the box representing the step

Short info - short description of the step that is shown in a bubble when the end-user views a map of the process and moves the mouse over the step

One form only - when checked the end-user will not be able to fill more then one form designed for this step.

A person should be attached before the step can be started (concerns tab) relevant only if Concerns person is checked in the Process properties. When checked prevents the user to start this step until a person is attached to the process. Not available for trial.

An organization should be attached before the step can be started (concerns tab) relevant only if Concerns organization is checked in the Process properties. When checked prevents the user to start this step until an organization is attached to the process. Not available for trial.

Status - regulates possibility to see/use/change the process definition. Explanations see in the table below:

Button Advanced - open a new window for advanced properties (described below). Not available for trial.

Button Reports - open a new window for reports definition (described elsewhere). Not available for trial.

Button Description - opens a simple editor window. The text will be seen when the user views the process map from the repository and double clicks on the step.

Note: Buttons "Advanced",  "Reports" and "Description" are enabled only after a step has been first created.

Advanced properties

Advanced properties are shown in the window below. They allow to send a message to an external server on the event happened in a process of the given type. To arrange message sending on changes you need to give an external server an method name as well as what you want to send to the server, e.g., all fields from an electronic form coded in an XML format. You can send all information about the step or part of it, e.g. <step_owner>, or <process_owner>. Detailed description of parameters is placed elsewhere)