Deploying a Nintex RPA Solution

Before deploying your Nintex RPA solution, it is best practice to perform these steps:

Manage automation environments

When moving wizards from development environments to production environments, ensure that each environment is used solely for its designated purposes, as described in Developing an Nintex RPA Solution.

When managing automation environments:

• Ensure that access and permissions for the different environments are controlled.

• Ensure that the folder structure (folder names and hierarchy) in the Nintex Studio is standardized across all environments.

• When accessing named resources (such as specific files, folders, or servers) that vary between the development environment and the production environment, use environmental variables on the respective systems instead of manually changing these values are moving a wizard from one system to another.

Migrate wizards

Wizard migration includes exporting wizards from the development environment and importing them into the production environment.

• When you export wizards from the development environment, only export standalone wizards or main wizards. Embedded wizards are packaged together with the main wizard when it is exported.

• When you import wizards into the production environment, ensure that the import is performed at the Library level to maintain the folder structure.

Review the Nintex RPA deployment checklist

• Ensure that all robots have been onboarded.

• Ensure that the robot environments are set up (connectors, browser settings, required 3rd party applications have been installed, and so on).

• Ensure that the accounts for the applications have been created and credentials have been entered into the Nintex Credentials Vault, as necessary.

• Ensure that the accounts for the applications are working and access rights have been granted accordingly.

• Ensure that the robot (account used) has access to the relevant shared folders and other resources (if necessary).

• Ensure that environment variables are set accordingly.

• Perform sanity test runs after wizard migration to ensure that the robots are functioning correctly.

• Ensure that triggers (and sensors for attended automation) have been set up correctly.