Process Mining Requirements

Process Mining compatibility with Decisions

Process Mining is only compatible with Decisions v8.5 and higher. It is recommended that both Process Mining and Decisions are operating on the latest version for optimal compatibility.

Decisions v8.9 and above uses Decisions.ProcessMining module. This module was changed from XML to JSON in v8.15 and above. Thus, it is important to update the Decisions to the latest version. For more information, contact support@decisions.com.

Process Data Requirements

Process data must track at least the following three data variables in their event log:

Data Member	Description	Example
Case ID	A unique ID is shared among the events within the same process but distinguishes different process executions from one another: the "who" behind the execution.	AccountID, LoanID, Name, any other identifiable information
Activity	Steps within the process must share the same names, not necessarily sequence, between all executions. This distinguishes between events within the same execution, the "what" and "how" behind the execution.	Inspect Damage, Obtaining Approval, Register Claim, and any other workflows within a process, such as Subflows with a parent Flow
Timestamp	Records the occurrence of each event within an execution. This is necessary to chronologically order the events within execution and compute durations between process steps. While only the start timestamp is necessary, including an end timestamp allows computing process step duration, the "when" behind the execution.	Date/time of occurrence

Data Member

Description

Example

Case ID

A unique ID is shared among the events within the same process but distinguishes different process executions from one another: the "who" behind the execution.

AccountID, LoanID, Name, any other identifiable information

Activity

Steps within the process must share the same names, not necessarily sequence, between all executions.

This distinguishes between events within the same execution, the "what" and "how" behind the execution.

Inspect Damage, Obtaining Approval, Register Claim, and any other workflows within a process, such as Subflows with a parent Flow

Timestamp

Records the occurrence of each event within an execution. This is necessary to chronologically order the events within execution and compute durations between process steps.

While only the start timestamp is necessary, including an end timestamp allows computing process step duration, the "when" behind the execution.

Date/time of occurrence

In addition to these required data members, the following optional, supplementary data variables to further define and refine your optimization:

Resource

Lifecycle

Case Attribute

Data Structure Requirements

Process Mining accepts external data from other software such as Jira, Salesforce, and ServiceNow and internal data.

Process Mining requires its supported Data Structures to enable the Enable Process Mining setting located in the Data Structure creation dialog to access its features.

The following Data Structures support Process Miner features:

Need to transfer data from a different data structure into one that supports Process Mining?

Please refer to the Importing and Exporting Data From Data Structures article for a step-by-step explanation.

Process Mining compatibility with Decisions

Process Data Requirements

Data Structure Requirements

What's Next