Package deployment

Note: 
  • Solutions is currently in beta. The changes described in this topic are only available to the customers participating in the beta program. For more information, see the Nintex Beta terms document.

  • Availability of this feature depends on your license and requires switching to the Nintex CE Platform. For information about the Nintex CE Platform, see Platform Experience; for information about your license, reach out to your Account Manager; and for information about trialing this feature, see Free Trials.

You can deploy packages to the same environment, a different environment, or another tenant. Packages contain the assets and configurations required for a solution deployment, such as workflows, tables, apps, documents, and related configurations. Solution supports both single-tenant and multi-tenant deployments.

Jump to:

Package source

The Package source setting specifies the environment used to create packages for a solution. The selected environment acts as the source environment for package creation and deployment. Only the selected package source environment can create packages for the solution. The source environment also determines who can view packages in the package list. Only Solution owners in the source environment can view the packages created from that environment.

Changing the package source updates the environment used for future package creation. Package source environments are typically configured as Development, Test, or Production environments. For more information, see Environments.

Access and manage Package source

Important: You must be a Solution owner to change the package source.

  1. Select the solution you want to update the package source for, then go to Settings. For more information, see Assets.

  2. Click on the General.

  3. Under Package source, select the environment where packages can be created for this solution.

Package source permissions

The package source environment determines package visibility in the package list. Only Solution owners in the source environment can view packages created from that environment.
Solutions support the following design-time roles:

  • Solution owner: Can create, manage, package, deploy, and delete solutions in environments where they have Solution owner access. Can also manage solution permissions and change the package source environment for a solution.

  • Solution builder: Can create and manage assets in a solution. Cannot rename, package, deploy, or delete solutions. Cannot manage solution permissions or change the package source environment for a solution.

Deploy a package

To deploy a package:

  1. Create a package for the solution. For more information, see Create a package.

    After the package is created, the Package created dialog is displayed.

  2. To select the target environment, click Go to target environment.

    The target environment opens in a new browser tab.

  3. Review the package contents in the Confirm deployment dialog.

  4. Click Install.

    The package contents are installed in the selected target environment.

Single-tenant deployment

In a single-tenant deployment, packages are created and deployed within the same environment. Use this deployment model to apply solution changes in one environment. Before deploying a package to users, review and validate the changes in the same environment. To test changes in a separate environment before release, contact your administrator to add another environment.

Multi-tenant deployment

In a multi-tenant deployment, packages are created in one environment and deployed to another environment. The package source identifies the environment where the package was created. Use this deployment model to manage solution changes across separate customer, regional, or organizational environments.

For example, create a package in a development environment, then deploy it to a production environment after the changes are reviewed and approved.

Deployment history

The Deployment history section displays the deployment details for a package version.

The following is displayed for each deployment:

  • Deployment date: The date and time the package was deployed.

  • Initiated by: The user who started the deployment.

  • Outcome: The deployment status, such as Successful.

  • Deployment log: The deployment log is a downloadable JSON file that helps troubleshoot issues during package creation and deployment. If an issue occurs, review the deployment log for additional details or share the log with Nintex Support for troubleshooting.
    The deployment log contains two main sections:

    • deployment: Provides deployment-level details, such as information about the deployment, package, solution, and status.

    • DeploymentLogs: Provides detailed deployment status for each asset in the solution, including the execution timeline, sub-actions, and results.

      • If an error occurs during deployment, review DeploymentLogs for the raw error message and related details.

      • If a deployment is partially successful, review the deployment log to identify which assets were deployed and which assets failed.