Workflow Designer

In Kuika Space, you can create applications with or without workflows. Your application is rendered without workflow when it is first created. If you wish, you can add a workflow to your app by clicking Add Workflow on the navigation bar on top of your Screen Designer:



Here in Workflow Designer, you build workflow of your apps, which links screens to specific workflow steps in a proper way regarding the purpose of your app.


  • Toolbox: Flow design toolbox is the flow step menu. You can select a flow step from this menu and drop it to canvas.
  • Flow Steps: You can design the flow of your app by using flow steps.


In Figure you see a one-step flow design, including only a start node, User action step and an end node. User action step stands for a screen in the app.

Flow Step Types

  • User Action:  a step type which requires human computer interaction.
  • Email Notification: an auto action step which does not require human computer interaction. In this step an email will automatically sent to a recipient / recipients. Email has a sender, a receiver / receivers, a topic and a content, to be specified during app design.
  • Push Notification: an auto action step which does not require human computer interaction. It informs user that an action has taken place.
  • SMS Notification: an auto action step which does not require human involvement.
  • Start Workflow: a step that serves for activating another workflow.
  • Time Delay: a step that make the workflow halt for an amount of time. Analyst should define time of waiting in app design process.
  • Decision: Decision step can be used to include conditional state changes in a workflow. The next step is determined according to the result of a boolean expression. Having two booleans (true and false), there are two candidate next steps.
  • Start Node: Start node is the initial node of the workflow. Every workflow must have a start node.
  • End Node: End node is the node in which the workflow is finalized. Every workflow must have an end node.


  • Workflow Design Canvas: The flow design canvas is the area that you can drop workflow steps to create your workflow.
  • Step Properties Panel: This panel involves information about a workflow step. One can use this panel to manage and monitor attributes of a workflow step.


For a workflow to be a complete and valid one there are some rules and requirements. Designer informs you during you design your app and helps you fulfill.

Some requirements per step can be seen below:

  • There must be one Start  and one End node.
  • End node must be reachable from every other step.
  • Routing variable of User Action shall not be empty.
  • User Action step must have a bound screen.
  • Email Notification must have a body, title and a recipient.
  • Sms Notification must have a body and a recipient.
  • Both out ports (true and false) of a Decision step must be linked to some other step.


To see how Workflow Designer works, let’s exercise through an example:

Let’s say you want to design an app having two screens. In the first screen the user will select a branch among the branches of a shop. In the second screen will pick a customer from a list of customers of that branch. Then an email will be sent to the selected customer.

Putting aside the screen designs, let’s look at the workflow step designs:

Element Properties Panel:

You will need three workflow steps: First and second steps will be User Action steps, third an Email Notification.

You can see properties of the steps in Element Properties panel:

  • Workflow Step Settings:  You can rename a workflow step through this subsection.
  • Bound Screen: Here is where you bind a screen to a workflow step.

In the scenario above, you will need to bind the screen to the User Action step. Email Notification step will have no screen bound as email notification is an auto action.

  • Create a new screen: You can create a new screen and bind it to your workflow step through this section.
  • Step variables: here you can assign expressions to the variables of your workflow step.

The variables of a User Action step are:

  • User Action Routing: This variable keeps unique ID of a the Kuika user to whom the workflow step routes.
  • User Action Routing Message: You can enter a note about the workflow step, to be seen by the routed person.

In our scenario, the first step is Pick Shop. The Pick Shop step will be routed to whomever is specified in its User_Action_Routing variable.

When Pick Shop step is completed, Pick Customer step will be activated, and will be routed to whomever is specified in its User_Action_Routing variable.

When the Pick Customer step is completed, an auto step Send Email will begin. It has no screens bound. An email will automatically be sent and the step will end.

Email Notification related variables are:

  • Email Notification emailBody: You can specify email body content via this variable.
  • Email Notification emailRecipients: You can specify the recipients via this variable by setting it to an email address.
  • Email Notification emailTopic: You can specify a topic to your email via this variable.