Workflows and Automation

 Browsers and support for HTTP have been diminishing, usually moving to HTTPS would be recommended.  Furthermore, later version of K2 (5.5) will only support HTTPS/SSL so conversion will be necessary. You can reconfigure K2 to use HTTPS by using the Setup Manager.  At a high level: - provision trusted SSL certificate, add to K2 server, reconfigure K2 site bindings for SSL/HTTPS - Run the K2 Blackpearl and K2 Smartforms Setup Managers and configure the sites to use HTTPS as the default - If K2 five, K2 Five Setup Manager - If still using SmartObject services, you may have to convert it to HTTPS as per below, as the HTTP/HTTPS scheme when making a request from client to server will usually have to match: https://help.nintex.com/en-US/k2blackpearl/DevRef/4.7/default.htm#Windows_Authentication_with_SSL_for_K2_SmartObject_Services.html - If still using K2services subsite to start workflow, you may need to also make web.config changes to enable HTTP/SSL as per: https://help.nin...

Updating K2 Service and App Pool Service Accounts Recommended Method: Use the Setup Manager: Access the K2 Setup Manager. Uncheck the "K2 Service" and "IIS App Pool" options. Enter the new password in the appropriate fields. Proceed with the setup process. Manual Method (if necessary): Update Windows Services and App Pool Identity: Update the password for the K2 Windows Services and K2 App Pool Identity. Important note for Exchange users: If using Basic Authentication with Exchange: Run ConnectionStringEditor.exe to update the password. If using OAuth Authentication (in later versions): Password update is not required. Update Service Instances (if applicable): If any K2 Service Instances use Basic Authentication, update their passwords as well. Crucial Reminder for Manual Updates: Ensure consistency for future reconfigurations: If you update passwords manually and need to reconfigure K2 later: Uncheck the "K2 Service" and "IIS App Pool" options i...

With K2 Cloud, you will not be able to create AD users, but there are SmartObjects available to create AAD users.  Users created in AD can be synchronized to AAD using Microsoft toolings. However, By Granting Read/Write to AAD as per the article below, you can manage AAD Users and Groups: https://help.nintex.com/en-us/k2cloud/userguide/current/default.htm#servicebrokers/azuread/aad-management.htm You will be able to use the following SmartObjects from the AAD service type: User SmartObject Group SmartObject User and Groups SmartObject

 Want to see what the K2 Setup Manager is doing when you install, upgrade or configure K2? 1.  Download and install on K2 server Notepad++ https://notepad-plus-plus.org/downloads/ This tool also has the benefit of: - if you are editing 'hosts' file or web.config file and forget to Run in Administrator mode (compared to when using Notepad), Notepad++ will launch relaunch in Administrator mode for you and keep the changes you have made, allowing you to save without having to redo these changes 2.  In Windows Explore, type in %temp%, this will put you in the current user's temp directory - you may see the 'K2 Setup Log' folder right away, where there installertrace logs will be - or if not you may have to navigate up one directory until you see the K2 Setup Log folder 3.  Open InstallerTrace logs in Notepad++ 4.  Click on the eye icon (tail log) and profit Now don't have to be in the dark about why it is taking so long or what it is doing.

If using validation pattern in a view or form, when you create a package (.kspx); validation pattern are included in the Additional Items section and will deploy to the target environment if does not exists. If you make a change to a validation pattern, it will be included in the package but the default option will be use existing.  To update validation pattern in the target environment using P&D, make sure to change it to Overwrite Existing. Validation pattern are global, so once you make a change to a pattern in any view/form, the update will affect any views/forms that uses it.  So in theory, you can also just use a test view or form in the target environment if you want to manually update a validation pattern.

1. Do you need or want to upgrade to a newer Windows Server version? If yes: Not recommended: In-place upgrade of Windows Server, followed by in-place upgrade of K2. Only consider this with careful backups and testing. Recommended: Set up a new Windows Server. This involves: Backing up the database Installing K2 on the new server Preserving the option to roll back to the old server if needed 2. Is your K2 setup standalone or a farm? If standalone: Using hostname for K2 site binding: This requires the most migration work, especially with a new server hostname. Consider reconfiguring to a farm setup for easier future migrations. New server with same hostname: Less manual updates needed. New server with different hostname: More manual reconfigurations required, including SharePoint integrations. Using DNS for K2 site binding: Migration is simpler. Consider reconfiguring to a farm setup for future benefits. If farm setup: Usin...