ee.telekom.workflow.api

Interface DslVariable<Level>

All Superinterfaces:

DslExpression<Level>

public interface DslVariable<Level>
extends DslExpression<Level>

DSL for workflow definitions.

Author:

Erko Hansar, Christian Klock

See Also:

WorkflowDefinition

Method Summary

Modifier and Type	Method and Description
Level	value(int id, Object value) Store the given constant value or expression result into the environment under the variable name from the previous node: .variable( "name" ).value( 1, "Heli Kopter" )

Methods inherited from interface ee.telekom.workflow.api.DslExpression

call, callAsync, humanTask, waitSignal

Method Detail

value

Level value(int id,
            Object value)

Store the given constant value or expression result into the environment under the variable name from the previous node: .variable( "name" ).value( 1, "Heli Kopter" )

NB! There is a Gotcha here: DSL parse time vs. workflow instance run time. All the java objects (for example new Date()) are created at the DSL parse time (server startup) vs. all the EL expressions (for example "${NOW}") are evaluated at the runtime when this workflow node is processed. So when you are doing .variable( "name" ).value( 1, new Date() ) then you are actually getting the server startup date value there, not the runtime moment, when this instance node 1 was processed. So you should use only constant values (like strings, numbers, enums etc.) as java objects, and EL expressions for creating runtime dynamic objects.

Parameters:

id - node id

value - variable value (any java object (only suitable for constants, see NB!) or "${EL_EXPRESSION}")