Deploying NWC/NAC workflows between tenants

Moving Workflows and Forms Between Tenants

To move a workflow to a different tenant (like from Development to Testing to Production):

  1. Export the workflow: This creates a special key for it.
  2. Import the workflow into the target tenant: This brings in the workflow itself and any forms used in its start or task steps.

Forms can also be moved independently:

  1. Export the form: This creates a .json file.
  2. Import the form into the target environment.

Important things to do first in the target environment:

  • Create connections: Make connections with the same names as in the original environment and give them the necessary permissions.
  • Remap data sources: For forms using lookup controls or external data, you'll need to connect those data sources again in the new environment.
  • Reconfigure rules mapping: If you have any rules that rely on specific fields or data, check and adjust those rules to make sure they work correctly in the new environment.

Remember:

  • Set up connections before importing workflows. Otherwise, you'll need to reimport them.
  • Always test workflows and forms thoroughly after moving them to a new tenant.

Comments

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7