All ideas

With an OIDC configuration with K2 from K2 5.9 it is not possible to change the response type sent to the authentication provider. This means that OIDC support is effectively limited to providers that support "id_token" and excludes others that on...

In K2 5.9, SmartForms JavaScript bundling and minification relies on Node.js resources that are extracted to the application pool service account's temporary profile directory: C:\Users\<AppPoolServiceAccount>\AppData\Local\Temp\SourceCode.F...

While there is a download button for workflows there is no upload button in the designer. This manual action would be good alternative to package and deployment tool especially for the staging of single workflows.

To automatically deploy workflows after the package and deployment a SmartObject e.g. of the Management API would be necessary to publish/ deploy the workflow. At the moment the only option is the manual deploy option in the designer for each work...

when implementing complex logic in rule, it would be very helpful to copy an existing rule into a new rule and change it after

Hi, When we have lot of provider instance or setup of a provider instance with a very small frequency like a refresh of 15 minutes, we can have quickly a table [SyncEngine].[RunHistory] very big. We saw up to 238 GB. In average it's 3.6 GB for 284...

Modern enterprises are rapidly adopting containerization to streamline deployment, enhance scalability, and improve resource utilization. Adding Docker support for K2 would enable: Simplified deployment and maintenance cycles Consistent environmen...

Hi, Currently if you want to get a serial number in the Workflow you have to use a workaround like https://community.nintex.com/nintex-automation-29/how-to-get-a-task-serial-number-in-the-workflow-27692 There is also a property called the "Serial ...

It can be difficult to know what has changed when using the package and deploy tool to move K2 forms and workflows between environments. If previous packages are kept for archive, it would be nice to be able to do a diff comparison between the two...

When we do lot of deployment of workflows, the table Server.LayerEntry growing quickly. In a customer case, it took more than 315 GB. It could be useful to have option to delete quickly some workflow version not useful anymore. Like script used in...