Welcome to the Synergy Technical Blog and Technical Knowledge Base – a resource that shares intelligent and creative solutions that have been built and implemented on real-time projects on behalf of Velocity clients.
We have previously talked about the different uses of K2 SmartForms expressions, but today we will be using these expressions in combination with conditional styling. The example we will be using is to display a progress percentage together with a progress colour for grouped activities.
The K2 Management Console is a crucial part of any K2 Project. You can manage workflow tasks, workflow roles & permissions, server rights, specify working hours as well as view and manage workflow errors.
For those of you that are familiar with a programming language, Data Fields can be seen as a variable. For those of you that are not, a Data Field is simply a place holder for information that can later be accessed from anywhere within the K2 workflow.
The simplest way to create a K2 Data Field is by using the K2 Context Browser. The K2 Context Browser can be accessed from various points throughout the K2 workflow. For example, when we create a new SmartObject Event, we are asked to choose the applicable K2 SmartObject. Even at this point we have access to K2 Data Fields. To view the available Data Fields or create new ones, open the Context Browser and click on the “Process/Activity Data” tab. Expand the “Data Fields” node in the tree view.
In this article, Part 4 of our series on validation with K2 SmartForms, we will be looking at server side validation. There are a few options available and the method below is by no means the only way to achieve server side validation, but it should suffice for the most common server side validation requirements.
Let first recall our sample application and just revisit what we are trying to accomplish. The client side interface of our demo application looks as follows:
Last week we gave you a brief introduction to the world of K2 Workflows by showing you how to create a new K2 Workflow project in Visual Studio 2013.
Now that we have an empty K2 Workflow project to work with, we can start to create the workflow.
A K2 Workflow consists of components dragged and dropped from the Toolbox onto the Designer and then connected with lines that indicate the flow. In this blog we’ll discuss one of these components: the Default Client Event.