Posts

Showing posts from April, 2023

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): Export the workflow: This creates a special key for it. 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: Export the form: This creates a .json file. 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 ...

K2 Upgrade Path 4.7 HTTP to 5.6 HTTPS

Upgrading K2 from 4.7 to 5.6 with HTTP to HTTPS Migration Prerequisites: New Windows Server and SQL Server for K2 5.6 HTTPS-enabled SharePoint environment Steps: Migrate K2 to New Environment: Install K2 4.7 on the new Windows Server and SQL Server. Configure K2 to use HTTPS by default. Set Up HTTPS SharePoint: Configure SharePoint to use HTTPS exclusively. Establish Secure Connection: Connect the HTTPS-enabled K2 environment to the HTTPS SharePoint instance. Repackage and Redeploy Solutions: Package solutions from either the old 4.7 environment or your Package and Deployment repository. During deployment, map to the new HTTPS SharePoint instance. This ensures correct HTTPS SharePoint service instances, category structures, and object system names. Thorough Validation: Validate that all solutions function correctly within the HTTPS K2 and HTTPS SharePoint environment. In-Place Upgrade: Perform an in-place upgrade of K2 from 4.7 to 5.6. Key Considerations: Carefully plan t...

Nintex Gateway for NWC/NAC

Troubleshooting "Tenant Name Does Not Exist" Error in Nintex Gateway Key Points: Prerequisite: Install Nintex Gateway before creating connections. URL Accessibility: Ensure required URLs are accessible from the server. Proxy Configuration: Verify proxy settings if applicable. Tenant Name Verification: Test tenant name with PowerShell. AAD SSO Considerations: Allow server access to SSO URLs for federated or SSO-enabled AAD. Troubleshooting Steps: Verify Installation: Confirm Nintex Gateway is installed. Check URL Accessibility: Contact IT to verify accessibility of: *.workflowcloud.com Region-specific  <region>.nintex.io  (e.g.,  eu.nintex.io ) gbo-cli-vib.nintex.io cdn.auth0.com nintex-portal.auth0.com Region-specific  *.servicebus.windows.net  (e.g.,  gwyprd01rlyneu01.servicebus.windows.net ) Address Proxy Settings: Configure Nintex Gateway for proxy if needed:  https://community.nintex.com/automation...