Process editor allows for verifying process execution with the use of a built-in simulator. Functioning of a process can be verified for different process configurations without the necessity of starting the BPM service.

To open the process simulator window, select button [Run], available from the level of the process modification window

In the process simulator window, a preview of analysed process is available.

Simulation will be started upon clicking on [Run] button and specifying tracking profile.

Buttons [Next], [Step Into] and [Step Ober] are active after the user selects his/her own breakpoints. A breakpoint can be set by clicking on a given activity and selecting [Breakpoint] button. A red dot will appear next to the selected activity. Now, during the elaboration, the process will stop after reaching that point. To resume the activity, user’s action is necessary.

During the simulation, activities have borders in three colors:

• Yellow – the activity is just being executed
• Green – the activity has been executed successfully
• Red – an error occurred during activity execution

Execution tracing and properties view are the same as in the case of process monitoring.

Parameter is a variable being a part of a process. To open a list of parameters, it is necessary to click on [Parameters] button, available in Model group of buttons.

A list containing all parameters defined within a user’s process, as well as default system parameters, is opened.

Each process has three default parameters:

• WorkflowInitiator – process initiator
  • UserName – name of the operator who has started the process manually or name of the operator for BPM service in the case of an automatic process startup
  • WorkflowUserId – operator’s ID
• Context – context in which the process is being executed
  • Instance – information about the process instance, its definition and type
  • Session – information about process session, center and company for which the process was started. This parameter can be used, for example, to retrieve a current center by its ID.
  • StartMode – information about the method in which the process was started
• WorkflowCreationTime– time of process initiation

To add a parameter, it is necessary to select [Add] button and select variable type and parameter’s textual type (Parameter column).

Additionally, it is possible to set the following options:

• Name – name presented for the user during the manual process startup
• Description
• Default Value– value assumed by a parameter if it is not specified by the user when starting a process
• Startup – if the option is checked, a parameter can be transferred from outside during a process startup. If the option is unchecked, also Value Required option is automatically unchecked.
• Value Required – after checking the option, a parameter is presented on the list during the manual process startup in the Comarch ERP Standard system and its value ca be set or changed. If the user does not select that option and the option Startup is checked, it is necessary to enter the default value.

Example

To transfer a file to a process, a new parameter named File, of FileDataType type, is added. The fields Startup and Value Required remain unchecked.

When starting a process for the File parameter, it is possible to select a file which will be transferred to the process. The path to the indicated file will be entered to the parameter.

Startup events enable automating starting of a process before or after execution of a specific operation in the Comarch ERP Standard system.

Startup events differ depending on process type (local or global). They can be selected when adding a new process or when editing a process, by selecting [Startup Events] button, available in Model group of buttons.

A list of startup events grouped by names of objects available in the system is opened.

On the left side of the window, it is possible to select those startup events, which will trigger a process. Along with an event, parameters can be sent to a process. They can be selected from the drop-down list of a given startup event. These values can be connected with parameters by means of mapping. Mapping section is located on the right side of the section containing startup event details.

Besides manual and automatic triggering of processes on an event, the system allows for starting processes according to defined schedules.

To add a schedule to a process, it is necessary to select [Schedules] button, available in Model group of buttons.

In case there are no defined schedules for a process, the system asks whether the user wants to create a new schedule. After answering Yes a window for defining a schedule with a list of schedules is opened, where it is possible to add new schedules and delete existing ones by means of [Add] and [Delete] buttons. On the left side of the view, details regarding schedule currently marked on the list, are displayed.

A schedule can be defined as daily, weekly, monthly or yearly.

Example

To allow a process to start automatically each last Saturday of a month, it is necessary to:

• Select Monthly schedule type
• Select option On the following day
• Select day – from drop-down lists it is necessary to select options last and Saturday
• Define period of schedule validity – in this case, it is necessary to select option every 1 mth, because the process is supposed to be started every month.

References refer to .dll assemblies which extend standard system functioning, e.g., by adding author activities. To use a given reference in a process, it is necessary to add it to the system. It is done by selecting button [Import] from References group of buttons which is available from the level of the process assembly and next, by selecting appropriate files from the disc.  It is also possible to export references.

After uploading references to the system, it is possible to add them to particular processes. In process edition window, it is necessary to click on [References] button, available in Model group of buttons.

On the list of references, there are standard references which cannot be deleted. Additionally, the user has access to standard assemblies for integrating the Comarch ERP BPM with Comarch Business Intelligence, Microsoft Office or Comarch Retail POS.

After being added to the system, own, dedicated references are automatically displayed on the list of references available from the level of process definition. After selecting a reference and clicking on [Apply] button, it is possible to use the created extension.

The functionality of contexts allows for assigning a global process to a Comarch ERP Standard object from the level of which the process is to be started. A list or object (e.g., invoice) detail can be used as a context. To define a context, it is necessary to select [ERP Context] button from Model group of buttons.

A window, where it is possible to assign values retrieved from a given context to specific process parameters, is opened.

In the section of startup parameters, there is a list of all user’s parameters marked as Startup. Below, there is a list of available objects of the Comarch ERP Standard system along with information about the type of a given parameter. Assigning an object to a parameter makes a process visible for a given object, whereas the value of such parameter, upon contextual startup, is automatically completed with the value of the object property.

Example

A process executes some operations on a purchase invoice document (PI). When starting the process from the level of the Task Inbox, as process parameters it is necessary to specify document ID and transaction date. So it is possible to define a context in such a way as to make it possible to start the process from the level of the list of PI and for document ID and transaction date to be completed on the basis of selected item. To do so, in the window of the context definition, it is necessary to associate process parameters with the list of purchase invoices (select object on the right side and click on [Assign]). Option Get Value should remain checked.

After applying the changes, saving the process, publishing it and assigning appropriate permissions, it will be possible to start the process from the level of the list of purchase in voices in the Comarch ERP Standard system.