Model is aggregated combination of nodes and arrows between them. Node is small business procedure/function which is changing some data or effect to business valued action(s).
Nodes can be server side or client side. Client side node always have associated role with it. Server side node have predefined role "SYSTEM".
Arrows is possible rout of documents. With client node unambiguously tied role. Workflow, usually, initiated by human. Other words by some clients node and finish on server side node. "START" node is begin of workflow, "FINISH" is end of workflow. During document movement between nodes, or between roles, we can manipulate with document's properties. The nature of those manipulation depends on developer. Document can not be promoted to next node until successful acknowledgment be received from from current node. If current step accomplished successfully than predefined variable ret must have value = true. Or ret=true; This action made by BP developer.
Routing based on messages (see. JMS).
What is DOCUMENT? Document is BP abstraction reflected as java-class. Using DFDesigner developer can define a set of fields. Those field became a simple Java class. Basically this class is data container. It can contains all required attributes for workflow and business operations. During workflow System can change attributes values using proper set or get method.
What is FIELD? Field is named variable. Developer can store some value into variable Using API to document developer can get collection of fields. Also document provide access management during workflow. Constraints can control fields behavior on UI. For example visibility editability, require to enter, values range etc.
See how it made in lessons.
| Contributions and
questions: Konstantion
Pupkov df@goodidea.ru icq:17631963 Copyright © 2004...2009 |