Analyzing Process-specifc Values from Designer Services

You can evaluate process information in Process Mining, for example in order to identify problems in a process. A pre-requisite for the evaluation is that the required process information is logged and transferred to Process Mining (refer to Collecting Logs in the Administration Guide for details).   

By default the following data is logged:

• Current Step

• End Date

• End Event

• Host

• Last Update

• Process ID

• Process Count

• Process Duration

• Process Name

• Step

• Step Duration

• Start Date

• Start Event

If you wish to expand the analysis with additional information on a process instance, you can widen the xUML service and log the values of customer-specific fields (also referred to as custom fields or custom values).

How to Log Process-specific Values for Usage in Process Mining

Process-specific content, for example values from form fields, can be transferred to Process Mining and used in analyses.

Restrictions for Designer Services

It is not possible to implement the logging for custom values with the following Designer elements:

• Start Event

• Message Start Event

• Timer Start Event

• End Event

If you want to create analyses for a service in process mining, you must first activate the log collection for this service. This is done in the process mining administration. Refer to Collecting Logs in the Administration Guide for details.

Currently, log collection is possible:

• In Docker setups for services with deployment target Integration.
  If you wish to log process-specific values for services with deployment target Container, please contact the Scheer PAS support team for advice.

• In Kubenetes setups for services with deployment target Container.