Copyright © Cloud Software Group, Inc. All Rights Reserved

About XPDL Entities Transformed From iProcess

This section describes how the elements that make up each iProcess entity are transformed into the elements that make up the XPDL entity. For example, the ID and name for an XPDL WorkflowProcess entity is derived from the procedure name of the iProcess entity.

Procedure Package

XPDL has the concept of a procedure package. There is no equivalent concept in iProcess. When an iProcess procedure is transformed into XPDL, the following iProcess extended attributes become part of an XPDL procedure package entity:

•	MadeBy – Tibco-Process-Suite.

•	tSchemaFormat – Schema Format Version information.

Procedure

An iProcess procedure maps to an XPDL WorkflowProcess. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Description
Procedure Name	WorkflowProcess ID and Name	The ID and Name of the XPDL WorkflowProcess
	WorkflowProcess Access Level	Can be either PUBLIC or PRIVATE • PUBLIC = Main procedure • PRIVATE = Sub-procedure or Sub-procedure I/O Parameter Template

There is no equivalent of an iProcess I/O Parameter Template in XPDL. These are stored as an XPDL WorkflowProcess with no activities or transitions. The ProcProperties extended attribute can be used to distinguish I/O parameter templates from other procedures. For example, ProcType element = IOTEMPLATE rather than MAIN or SUB

Sub-Procedure Input/Output Parameters

iProcess Sub-procedure input/output parameters are mapped to XPDL WorkflowProcess Formal Parameters. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Descriptions
Sub-Procedure Parameter ID	FormalParameter ID	FormalParameter ID is the sub-procedure parameter ID appended by either ip or op • ip for input • op for output
	FormalParameter Mode	FormalParameter Mode is either IN or OUT • IN is for input parameters • OUT is for output parameters

Note that:

•	iProcess sub-procedure I/O Parameters are separated into input and output parameter sections (in XPDL all parameters are defined in one section and referenced according to their sequence).

•	iProcess sub-procedure I/O Parameters have unique IDs within their section. This means you may have a parameter in the input section with the same ID as a parameter in the output section.

•	When transferred to XPDL, parameter IDs are appended with ip (input parameter) or op (output parameter) to ensure that they are unique within the XPDL parameter definitions.

•	The complete I/O parameter definitions are also stored within the ProcProperties/SubProcParams extended attribute as only a representation can be stored within generic XPDL.

Field

An iProcess field maps to an XPDL WorkflowProcess DataFields or DataField. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Descriptions
Field Name	ID and Name	The ID and name of the XPDL field
	IsArray	IsArray is either YES or NO depending on whether or not the field is an array
Field Length	Length	The length of the field
Field Data Type	Data Type	Data Type is one of the following: • STRING - text/memo fields • FLOAT - numeric fields • DATETIME - date fields • DATETIME - time fields • REFERENCE - All other fields

Normal Step Form Definition

An iProcess normal step field definition maps to an XPDL WorkflowProcess/Applications/Application. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Descriptions
Work Item Step Name	ID
	Name	is TIBCO-Process-Suite-WorkItem which indicates the application to process the form
Field Markings	FormalParameters	For each field marking on the form definition a FormalParameter is output. The FormalParameters are made up as follows: • ID = Fieldname and Unique ID. This is to ensure that there are not duplicate IDs where two or more instances of the same field appear on the form • Mode = Field Marking Type. It can be one of the following: • IN = DISPLAY/EMBEDDED • OUT = CALCULATED/HIDDEN • INOUT = REQUIRED /OPTIONAL • DataType = is one of the following: • STRING - text/memo fields • FLOAT - numeric fields • DATETIME - date fields • DATETIME - time fields • REFERENCE - All other fields

EAI Step Type Definition

An iProcess EAI Step Type Definition maps to an XPDL WorkflowProcess/Applications/Application. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element
EAI Step Name	ID
EAI Type Name	Name

No FormalParameters are output.

Complex Router

An iProcess complex router maps to an XPDL activity with Type Route. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element
Numeric Object ID	ID
Complex Router Name	Name

Condition

An iProcess condition maps to an XPDL activity with Type Route. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element
ID	Numeric Object ID
	Name	is Condition_Router

Note that: • The Condition expression is placed on all Transition/Condition’s from the XPDL activity that are created from outgoing ‘true’ links • All false links from the condition object are defined as ‘otherwise’ transitions from the XPDL activity

Dynamic Sub-Procedure Call

An iProcess dynamic sub-procedure call maps to an XPDL Activity with Type Implementation/No. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Description
Numeric Object ID	ID
Dynamic sub-procedure call name	Name
	StartMode	is Automatic
	FinishMode	is Automatic
Deadline	Deadline	The deadline is made up as follows: • Execution is either SYNCHR or ASYNCHR: − SYNCHR = Withdraw on expire − ASYNCHR = Do not withdraw • Condition is the textual representation of the deadline expressions/period • Exception name is the unique reference to the deadline transition ID in the following format: DeadlineExpired_trans_uniqueid Note: The complete deadline is also stored as an extended attribute.

EAI Step

An iProcess EAI Step maps to an XPDL activity with Type Implementation/Tool/Application. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Description
Numeric Object ID	ID
EAI Step Name	Name
	StartMode	is Automatic
	FinishMode	is Automatic
	Deadline	The deadline is made up as follows: • Execution is either SYNCHR or ASYNCHR: − SYNCHR = Withdraw on expire − ASYNCHR = Do not withdraw • Condition is the textual representation of the deadline expressions/period • Exception name is the unique reference to the deadline transition ID in the following format : DeadlineExpired_trans_uniqueid Note: The complete deadline is also stored as an extended attribute.
	Implementation type.	The implementation type is made up as follows: • Tool[Type = APPLICATION]. The EAI Type specific definition data is stored as an XPDL WorkflowProcess/Applications/Application • Tool Id = EAI step name • ActualParameters = unused (all fields used in application are references to procedure field definitions). For more information on EAI type specific definitions in XPDL Applications see EAI Step Type Specific Definitions • Performer = <EAIStepName>_Performer. This references an XPDL WorkflowProcess/Participants/Participant that specifies the first Addressee of the step. (XPDL only allows a single participant definition)

Event Step

An iProcess event step maps to an XPDL activity with type implementation/no. The following table shows the transformation details for this entity

iProcess Element	XPDL Element	XPDL Element Description
Numeric Object ID	ID
Event step name	Name
	StartMode.	The StartMode is configured as follows: • Automatic if the event step is part of the workflow. For example, if the event is processed as an action of another step and halts the branch until the event is triggered • Manual if the event is not part of the workflow. For example, it can be triggered asynchronously
	FinishMode.	The FinishMode is Manual. For example, a user or external application triggers it
	Implementation type	The implementation type is made up as follows: • Tool[Type = APPLICATION]. The EAI Type specific definition data is stored as an XPDL WorkflowProcess/Applications/Application • Tool Id = EAI step name • ActualParameters = unused (all fields used in application are references to procedure field definitions). For more information on EAI type specific definitions in XPDL Applications see EAI Step Type Specific Definitions • Performer = <EAIStepName>_Performer. This references an XPDL WorkflowProcess/Participants/Participant that specifies the first Addressee of the step (XPDL only allows a single participant definition)

Graft Step

An iProcess graft step maps to an activity with type implementation/no. The following table shows the transformation details for this entity

iProcess Element	XPDL Element	XPDL Element Description
Numeric Object ID	ID
Dynamic Sub-procedure Call name	Name
	StartMode	is Automatic
	FinishMode	is Automatic
	Deadline.	The deadline is made up as follows: • Execution is either SYNCHR or ASYNCHR: − SYNCHR = Withdraw on expire − ASYNCHR = Do not withdraw • Condition is the textual representation of the deadline expressions/period • Exception name is the unique reference to the deadline transition ID in the following format : DeadlineExpired_trans_uniqueid Note: The complete deadline is also stored as an extended attribute.

Start Step

An iProcess step maps to an XPDL activity with type route. A route activity with a single transition to default first activity in process. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element
Numeric Object ID	ID
	Name is Start

Normal Step

An iProcess normal step maps to an activity with type implementation/tool/application. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Description
Numeric Object ID	ID
Normal step name	Name
	StartMode	The StartMode is Automatic. The work item is automatically delivered to a work queue by the iProcess Engine.
	FinishMode	The FinishMode is Manual. The work item is manually released by a user.
	Deadline	The deadline is made up as follows: • Execution is either SYNCHR or ASYNCHR: − SYNCHR = Withdraw on expire − ASYNCHR = Do not withdraw • Condition is the textual representation of the deadline expressions/period • Exception name is the unique reference to the deadline transition ID in the following format : DeadlineExpired_trans_uniqueid Note: The complete deadline is also stored as an extended attribute.
	Implementation type	The implementation type is made up as follows: • Tool[Type = APPLICATION]. The EAI Type specific definition data is stored as an XPDL WorkflowProcess/Applications/Application • Tool Id = Normal Step Name • ActualParameters = Fields referenced by form definition mapped onto the Application defined for the form associated with this step. For more information, see Work Item Step Form Definitions. • Performer = StepName_Performer where: − StepName is the name you defined for your Step Performer references an XPDL WorkflowProcess/Participants/Participant that specifies the first Addressee of the step (XPDL only allows a single participant definition)
	WorkflowProcess/Participants/Participant	The WorkflowProcess/Participants/Participant is configured as follows: • Id is the step name_Performer (links to Activity/Performer) • Name is the iProcess user/role/field name • ParticipantType is configured as follows: − HUMAN = iProcess User/Group addressee (or “sw_starter” for user who initiated case (procedure instance)) − ROLE = iProcess Role addressee − RESOURCE = Data field addressee Note: As only the first addressee is transferable into generic XPDL, the complete Addressee definitions are also stored as an extended attribute.

Stop Object

An iProcess stop object maps to an XPDL activity with type route. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element
Numeric Object ID	ID
	Name is Stop

Note that • This is a route activity with a single transition from the last step in the process branch. • This object is optional and is inferred by an object with no output links.

Sub-Procedure Call Step

An iProcess Sub-Procedure Call Step maps to an XPDL Activity with Type Implementation/Subflow. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element
Numeric Object ID	ID
Sub-Procedure Call step name	Name
	StartMode	is Automatic. The sub-procedure is automatically called by the iProcess Engine.
	FinishMode	is Automatic. The sub-procedure is automatically called by the iProcess Engine.
	Deadline	The deadline is made up as follows: • Execution is either SYNCHR or ASYNCHR: − SYNCHR = Withdraw on expire − ASYNCHR = Do not withdraw • Condition is the textual representation of the deadline expressions/period • Exception name is the unique reference to the deadline transition ID in the following format : DeadlineExpired_trans_uniqueid Note: The complete deadline is also stored as an extended attribute.
Sub-Procedure Name	SubFlow ID
	Subflow Execution	Subflow Execution is always SYNCHR. iProcess procedures do support calling a sub-process asynchronously. To configure this, you need to define a branch in the procedure and call out the sub-process on the branch.
The expressions (where a valid expression can be simply a reference to a field) mapped onto the sub-process I/O parameters	SubFlow Actual Parameters	Note: the complete parameter mappings are also stored as extended attributes. This is because in an iProcess procedure these mappings are made via unique Id’s for each parameter whereas XPDL relies on the correct sequencing of parameters.

Transaction Control Step

An iProcess transaction control step maps to an XPDL Activity with Type Implementation/No. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element Description
Numeric Object ID	ID
Transaction Control Step Name	Name
	StartMode	is Automatic
	FinishMode	is Automatic

Wait Step

A wait step is the iProcess procedure equivalent of an XPDL ‘AND Join’ (i.e. waits for all steps on incoming procedure branches to complete before continuing along a single branch). All other joins (multiple transitions into a single activity) are treated as ‘XOR Joins’. A wait step maps to an XPDL Activity with Type Implementation/No. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element
Numeric Object ID	ID
	Name is Wait_Router

Link

An iProcess link maps to an XPDL Transition. The following table shows the transformation details for this entity.

iProcess Element	XPDL Element	XPDL Element
	ID .	is trans_uniqueid where uniqueid is an automatically generated unique ID
	From/To	From/To are the object IDs that the link connects from and to
Link label text	Description
	Condition type	The condition type is configured as follows: • CONDITION. This contains the contents of the condition expression if the link is a link from a condition step’s true action. • OTHERWISE. If the link is from a condition step’s false action, an OTHERWISE transition type is created. Multiple false links create multiple OTHERWISE transitions. • EXCEPTION. If the Deadline link contents of the Condition reference to the ‘from’ activity’s Deadline/ExceptionName value (i.e. “DeadlineExpired_Trans_uniqueid”).
	Activity/TransitionRestrictions/Transition Restriction	These are defined only when there are multiple links to and from a single object. They are configured as follows: • Multiple links from an object are created as AND types. This is because iProcess uses nested routing object constructs to define complex conditional paths. • Multiple links to an object are created as XOR types. If the object that is being linked to is a Wait step then it is created as an AND type.

This does not include Withdraw Step Links. These are stored as WorkflowProcess level Extended Attributes.

Annotation

An iProcess annotation maps to an XPDL ExtendedAttribute/ExtAttr/NonFlow
Object with sub-element AnnotationObject.

EIS Report

An iProcess EIS report maps to an XPDL ExtendedAttribute/ExtAttr/NonFlow
Object with sub-element EISObject.

Link Router

An iProcess link router maps to an XPDL ExtendedAttribute/ExtAttr/NonFlow
Object with sub-element ElbowObject.

Script

An iProcess script maps to an XPDL ExtendedAttribute/ExtAttr/NonFlow
Object with sub-element ScriptObject.

Copyright © Cloud Software Group, Inc. All Rights Reserved