Basic Terminology

Process: A process is a repeating business workflow (i.e., it has been executed at least twice). A process is defined by a common start point and endpoint.

Process Occurrence: Process occurrence refers to the number of times a process has been occurred and identified.

Process Variant: A process variant is a sequence of steps (actions) by which a user executes a process. A single process can have many variants – i.e., many different ways by which the users got from the common start point to the common endpoint.

Action: An action is a single step in a process.

Team: Teams are organizational segments or units that share a single Discovery Server. All Process Discovery settings and data are managed individually by Team. Nintex Console users may have permission to access the data of one or more Teams. You can think of a Team as a department in your organization, e.g., Finance, Sales, etc. Having multiple Teams is beneficial because it allows you to categorize and organize the data collected from each department, division, team, or group within your organization. This segregation enables you to easily identify the source of a process when viewing or selecting it.

Candidate Process: Candidate Process refers to a process that was automatically discovered by the system as a process with potential for automation. Such processes are available for you to review before you add them to your library.

How does it work? 

Process Discovery analyzes recorded user-actions and examines screenshots to identify process repetition, similarities in users' actions, and commonalities among computed processes and tasks. After analyzing all the data, the system generates a mapping of action sequences. Each sequence is then evaluated and ranked by the system based on its length, repetition, and volume. Sequences that receive high rankings are identified as Candidate Processes.