Process Library
The Process Library page displays a table of all the processes that the Business-Analyst selected and added from the Discovery page. From the Process Library page, it is easy to dig deeper into the details of each discovered process by accessing its details.
Column headers in the Process Library table
| Property | Description |
|---|---|
| Process name |
Name you have assigned to the process. (Until you give the process a name, a system-generated process name will appear in this column) - see Naming Processes. Directly under the process name appears the number of subprocesses (if any) detected within the process. |
| Status | Shows if the process was successfully added to the library. |
| Business Use Case |
Provided by the Business Analyst when adding a process to the library. You can define several processes under a single business use case. |
|
Team (tenant) |
The Team in which the process was discovered. This column will only be visible if: (1) the Nintex Process Discovery deployment in your organization has more than one Team; (2) processes have been discovered in more than one Team; and (3) you have permissions to view data for more than one Team. |
| Occurrences |
The number under Occurrences reflects how many times the process has been detected (how many times users were recorded performing this process). |
| Min Actions |
The lease amount of actions performed in the process (like mouse clicks and keyboard strokes). |
| Min Duration |
The shortest occurrence duration within the process. |
| Users |
Total number of unique users who have executed the process since it was first detected. Hover your mouse over the number of users to see a tooltip listing all users who have executed the process. |
| Applications |
A list of applications utilized in executing the process. |
| Recommendation |
To assist with process prioritization, Nintex Process Discovery will present an automation score based on ROI-related statistics collected automatically by the discovery algorithm.  How is this score determined?
The score is calculated using a proprietary formula, taking into account several variables, including:
In practice, the automation score can range from 0% to 100%. A higher score indicates a process with favorable characteristics, such as frequent occurrence, high average execution time, a significant number of user actions, and multiple variants. For example, a score of 100% may be assigned to a process that is frequently repeated, takes a significant amount of time to execute, involves numerous user actions, and has multiple variations. By considering these variables and their combined averages, the recommendation score provides insights into the potential value and suitability of automating a particular process. |