This section explains how to design Sybase WorkSpace Business Process objects in the PowerDesigner Business Process Model.
Service
In Sybase WorkSpace, a service is an interface to an external application or a business process. BSM (Sybase Base Service Model) is the native language used to describe a service. The BSM file contains the description of the entire Web service expressed by several port types. Each port type defines different operations. Sybase WorkSpace Business Process supports the following types of Web service operations:
Business Process
A business process is a particular service implemented by the orchestration of other services including several activities linked by a graph. This graph defines the choreography of the Process. The business process may have fault, compensation, and timeout handlers that are not linked to the main choreography.
Variables
Variables are named data type instances that are accessible by all activities within a business process definition. Variables can have simple data types (string, integer, float, or boolean) or XSD complex data types.
Partner Link
You design partner links using organization units in the business process model.
Service Invocation
Services represent the interaction with internal and external applications, such as a database, Java applications or an ERP system. A service may contain several interfaces and each interface may contain multiple operations. Each operation has a schema in the service that defines the operation inputs and outputs. A service interaction represents an activity that invokes a service operation of the following type:
Assign Activity
An assign activity is a sequence of atomic assign tasks. An assign task is an XPath expression that copies value from a variable to another variable. The assign task can be: a regular assign for setting the value of a context variable, a Get environment variable or a Get process Id that copies its value to a context variable, a Graft that adds nodes to an XML tree or a Prune that removes nodes from an XML tree.
Split-Join Activity
A split is a point in the business process where a single activity splits into two or more parallel activities. A join is a point in the business process where two or more parallel activities converge into a single common activity.
Complex Activity
A complex activity is made of atomic activities. Complex activities can end normally, after a timeout event, or after a fault event. The complex activity catches exception events (exception, compensation, or timeout) by using exception handlers, compensation handler and timeout handler.
Loop Activity
A loop activity is a complex activity with iterations.
Event Handling Activities
Events happen only within top-level process and complex activities. The different types of event handling activities are: exception, timeout, and compensation handling.
Delay and Terminate Activities
A delay activity allows the user to define a pause on the runtime processing and the delay for continuing the runtime processing.
Sequence Flow from Activities
A sequence flow is a control flow between activities. The link goes from a fixed out anchor in the source object to a fixed in anchor in the target object. Some objects like Start, Choice, Split, and complex activity may have more than one output coming from the same anchor. SingleRule may have more than one output going out, each one from a specific anchor. The remaining activities may have only one sequence flow going out from one anchor except terminal activities.
Correlations
A correlation is a set of identifying properties used by Sybase WorkSpace engine to identify the instance of a business process concerned by a received or a sent message.