In this post I will tell you about popup animations in K2 and how to add more fun into a K2 Smartform. You can either inject CSS/JS onto your form,…
I could not find a clear explanation on K2 Knowledge Center, how workflow versioning works in the new designer (K2 Five and/or K2 Cloud). I still receive some questions from my colleagues, therefore, I find it helpful to create a short article and explain all the details. However, you need to understand, that everything was tested on K2 Cloud Update 7 and K2 Five 5.2. K2 might change the behavior, which make the following article invalid. So let's go.
Recently I had an internal discussion within my team, that K2 Smartforms has a limited number of icons, that a user can use with the out-of-the-box controls, like buttons or data labels. We all agreed, that we need more. However, even if we have 1000 icons to be used with buttons, some other customers will always require more or something totally different. Therefore, I decided to write a short article to demonstrate, how you can quickly and easily add icon fonts in K2 to get almost unlimited number of icons for your purposes.
I already described how you can easily create a REST API to integrate K2 with a NoSQL database. However, in the demonstrated example you had to make a call to http://localhost:3000. This means that the application should be hosted somewhere locally, which might be a suitable approach when you use K2 Five. But it is definitely unacceptable, when using K2 Cloud. That is why I decided to explain to you, how you can quickly deploy your REST API to Azure App Service.
Such scenarios are not common, that you need to use K2 with NoSQL databases. However, I would still like to show the possibility of a K2 platform to connect to NoSQL databases to 'CRUD' data. Moreover, the REST API I am trying to show is kind of dynamic. The object schema as well as the collection you are working with completely depends on the swagger schema you use with K2 REST Broker. The current approach is also suitable for a K2 Cloud platform.
After release of Microsoft SQL Server 2016, Microsoft added a feature, which is called Row-Level Security. It allows users to control row permissions in a database table based on the characteristics of the user executing a query (for example, group membership or execution context). In this article I will try to describe the approach you can take to use Row Level Security with K2 and SQL ServiceBroker, when building K2 applications.