Process Capture FAQ

You can now automate the generation of process maps using AI-driven recording of your step-by-step activities, significantly enhancing efficiency, accuracy, and consistency across the creation of your new process documentation.

With Process Capture, you can easily create process maps from recorded user activities, making it a more user-friendly approach than traditional mining tools. This tool lets you quickly generate processes, ensuring alignment across all roles. Integrating activities, tasks, roles, and systems provides a clear understanding of everyone’s place in the process.

No, Process Capture is a new integrated feature within Process Managerand cannot be accessed without a Process Manager tenant. Process Capture will only be available as a feature within Process Manager - available to Expert and Enterprise tiers.

Process Capture will be enabled by default for all new customers on Expert or Enterprise tiers. Promasters A Nintex Process Manager system administrator who administers a Nintex Promapp site and has rights to view and edit all areas of a Nintex Promapp site. will then turn on the feature for the tenant using a configuration toggle under Admin > Capture, like other Process Manager features.

Process Capture will not initially generate BPMN process models, just Nintex process maps. We may support the generation of BPMN models in the future based on customer requests.

To capture step-by-step recordings of a process, you must first download and install the Process Capture widget (or have IT install it for you) on your local Windows machine. The widget requires elevated permissions (administrator) because a key is added to the registry. When active, the Process Capture widget records all user activity on your machine including desktop and web applications. For more information see Using Process Capture.

You don’t need an .MSI file to deploy the installer using a device management solution, such as Intune. Your IT team can create an install and uninstall PowerShell script to perform all the steps and then wrap that in an Intune package file using a Microsoft command line tool.

We cannot provide a generic .MSI file for all customers as the installation package also contains configuration and connection files that may be specific to the tenant.

For each user action (mouse event or keyboard action), a screen shot is taken. The widget also captures the following meta data: Mouse location, keyboard commands (shortcuts), URL / Process Name, window size and location, screen DPI and additional OS properties. Process Capture does not collect back-end information from log files or databases. The widget does not capture text strings typed by users such as passwords (though textual information is extracted from screen shots when generating a procedure).

Users with edit permissions to a specific process can start a capture, review and edit a capture, and generate a procedure from it. Additionally, it is possible to specify which Roles have access to the Capture tab and only these can capture, review, and edit captures.

Once a user stops the recording, they are taken to the Capture tab in Process Manager for the specific process. Users with edit permissions to a specific process can capture, review, and edit the capture and generate a procedure from it. In a future release, it will be possible to specify which Roles have access to the Capture tab and only these can capture, review, and edit recordings.

Recordings (screen shots + activity meta data) are stored in the Process Manager back-end (NSP). Data is stored in a separate collection for each customer and models are not cross-trained on other customers’ data.

Recordings will remain available for users in the Capture tab after generating a procedure. If a user deletes the capture in Process Manager, all data for the recording will be deleted from the database.

Users can record as many steps as they want, but currently only the first 200 actions can be used as inputs for procedure generation. If a Capture is longer than that, users can remove irrelevant actions until the first 200 actions contain all needed actions. If the process spans more than 200 relevant steps, users will have to do multiple Captures with procedure generations after each one.

In the current version, only one capture can be associated with a process. If a process has multiple variants, generating a procedure will append to whichever variant is currently selected. In the future, we want to add support for multiple captures being associated to a single process and even captures being associated to individual variants.

Workaround

While we only support a single capture per process at any one time, users can use this workaround to "pass the baton" with Process Capture:

• User 1 creates a capture and generates a procedure.

• User 1 deletes the capture.

• User 2 creates a capture and generates a procedure.

Since generating a procedure from Process Capture does not override existing contents but only appends, the Process will now contain all the Activities and Tasks from User 1's capture and User 2's capture.

After stopping a capture, users are taken to review the capture in Process Manager. Users can remove and prevent individual actions from being sent to the LLM, such as irrelevant actions or PII. When reviewing the capture, users can also decide whether to delete the entire capture and start from scratch or continue with the procedure generation.

When using the Process Capture feature, data supplied by users will be used to generate the procedure and may help improve the feature in the future. We do not train any models based on the data but may use the data to evaluate the performance and based on this apply manual tuning to improve the results (such as refining the prompt).

Users will need elevated Windows permissions to install the application and once running, it requires an internet connection to the Process Manager back-end just like normal Process Manager usage (no new ports or endpoints).

All sensitive data is encrypted both in transit and at rest. We use AES-256 and SHA-256 for all encryption processes and use HTTPS with TLS 1.2 for secure communication.

You can find the log files on the machine under %AppData%/ProcessCapture/logs.

If you hold down Shift + Win + Right/Left arrow, you can move the Capture window from screen to screen. Once a Capture has started, you can click on the six dots to drag the widget around.

If you add

"showRobotOnRecord": true

to %AppData%\ProcessCapture\config\settings.json, the Capture widget will show up when sharing screens (but with the side-effect of the Capture widget also being visible in the screen shots taken).