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 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 Nintex Process Discovery settings and data are managed individually by Team. Nintex Process Discovery 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. One reason you would want to have several Teams is to divide between the processes data collected on each department/division/team/group (AKA Team) in your organization. This way, when viewing or selecting a process, you can know which Team it was collected from. Teams are basically organizational segments or units that share a single Discovery Server .

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? 

Nintex Process Discovery runs through all the recorded user-actions, analyzes each screenshot, and looks for process repetition, similarities in users' actions, and common ground across users' computed processes and tasks. Once all the data is analyzed, the system maps out sequences of actions. Each sequence of actions is analyzed and ranked by the system on length, repetition, and volume. Highly ranked sequences are counted as Candidate Processes.