Jump to: navigation, search

Workflow


Revision as of 07:22, 24 July 2013 by JKN (Talk | contribs) (Created page with "==Overview== Workflows are a powerful way for adapting {{UBIK}} to any needs. They can be used as a replacement for the traditional way of customizing using code, or simply as...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Overview

Workflows are a powerful way for adapting UBIK® to any needs. They can be used as a replacement for the traditional way of customizing using code, or simply as an additional option to achieve a desired behavior.

What is it?

A workflow is a series of distinct programming steps or phases, where each step is modeled as an Activity. Such activities can be assembled visually into workflows using the Workflow Designer, a design surface that runs within various components of UBIK® Studio.

When to use?

This question isn't easily answered. In fact it is completely up to the user to draw the border between coding and workflows, or to draw a border at all, and one would most likely achieve the same results using either technique. However, here are some recommendations that might be helpful in picking the right turn:

Use coding for...

  • resulting behavior that is quite static and doesn't change a lot over time
  • very complex tasks
  • tasks where performance and resource consumption is an issue

Use workflows for...

  • business logic
  • dynamic tasks with ever changing parameters, where traceability is an issue
  • potentially long running tasks that will require persistence

See also

Workflow Editor Workflow Designer Code- and Workflow Debugger