<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Workflow Variables in cDevWorkflow

Posted by Kevin Sweeney on May 10, 2011 1:03:05 PM



Workflow Variables Using Workflow Variables


Each component of our cDevWorkflow designer tool set permits the use of a workflow variable.

Right out of box there are templates pre-built that will get you started.

It's true.

Even the initial start step let's you define workflow variable.   As you would expect with such a powerful BPM engine, all of these workflow variable templates are configurable.

Here is a screen capture of the start step workflow variable toolbox built into the software:

workflow variables

Once a workflow variable is defined as part of the workflow database, you write to or call data from their database locations to make decision criterion for workflow processing. To use a workflow variable for processing we must identify the variable and then create an evaluating expressions.

For example, let's say we start with a simple data field YES / NO type logic.  We simply want to insure that a purchase order amount been recorded?  The data field we will define contain a variable called: POAmount

But we can do more than flag a processing mistake with this data field.  The POAmount variable data field can be used as an input for a workflow decision by using the following syntax: Variable.POAmount

Now by adding an expression to the workflow variable, cDevWorkflow can evaluate and make a processing decision.  Before we were using this data field with YES / NO logic.  Asking the question: Has a purchase order amount been recorded?

This expression can create separate workflow steps or actions such as assign tasks and send emails to users for approvals.  In this example we will define our purchase order amount as the key criterion for making a decision point.  The expression would look like this:  Variable.POAmount > 125

Within the cDevWorkflow design tool we could define additional workflow process actions that will occur based on the purchase order amount.

  1. If POAmount is < 125 send email to User Group #2 for processing.
  2. If POAmount is > 125 send email to User Group #1 for processing.

A small sampling of the Workflow Technology for BPM Solutions contained within our cDevWorkflow product offering can be found here: Workflow Technology That Works.

[hs_form id="9"]

Learn more about our Process Automation & IT, QA Services or Software Development products and solutions on the Web!  Visit us at: Innovative Process Solutions

Topics: workflow variables, workflow variables in sharepoint, Blog, workflow variable, bpm variable, programming workflow variable, workflow process variables