WAPISUBWORK is the object handle of a sub-workflow. It is used in the WAPI functions for workflow manipulation operations.

Instance Attributes Index

o pWORKID
The unique ID for the workflow.
o pSUBWORKID
The unique ID for the sub-workflow.
o pMAPID
The ID for the map stored in the WMap table that will be used as the route definition for the sub-workflow.
o pRETURNSUBWORKID
The subWorkID for the sub-workflow that started this sub-workflow if it was started as a sub-workflow from a task.
o pRETURNTASKID
The ID for the task that started this sub-workflow if it was started as a sub-workflow from a task.
o pDATEDUE_MIN
The minimum possible due date for the sub-workflow.
o pDATEDUE_MAX
The maximum possible due date for the sub-workflow.
o pDATEINITIATED
The date the sub-workflow was initiated.
o pDATECOMPLETED
The date the sub-workflow was completed.
o pSTATUS
The status of the sub-workflow.
o pTITLE
The title of the sub-workflow.
o pPROJECT
The project identifier for the sub-workflow.
o pUSERDATA
Stored data that can be used by the sub-workflow.
o pCUSTOMDATA
Stored data from customization that can be used by the sub-workflow.

Instance Attributes

o pWORKID 
 Integer pWORKID
The unique ID for the workflow. The column in the WSubWork table is SubWork_WorkID.
o pSUBWORKID 
 Integer pSUBWORKID
The unique ID for the sub-workflow. The column in the WSubWork table is SubWork_SubWorkID.
o pMAPID 
 Integer pMAPID
The ID for the map stored in the WMap table that will be used as the route definition for the sub-workflow. The column in the WSubWork table is SubWork_MapID.
o pRETURNSUBWORKID 
 Integer pRETURNSUBWORKID
The subWorkID for the sub-workflow that started this sub-workflow if it was started as a sub-workflow from a task. The column in the WSubWork table is SubWork_ReturnSubWorkID.
o pRETURNTASKID 
 Integer pRETURNTASKID
The ID for the task that started this sub-workflow if it was started as a sub-workflow from a task. The column in the WSubWork table is SubWork_ReturnTaskID.
o pDATEDUE_MIN 
 Date pDATEDUE_MIN
The minimum possible due date for the sub-workflow. There is a minimum and maximum possible due date because a workflow can have multiple paths that can be taken based on conditional routing. The column in the WSubWork table is SubWork_DateDue_Min.
o pDATEDUE_MAX 
 Date pDATEDUE_MAX
The maximum possible due date for the sub-workflow. There is a minimum and maximum possible due date because a workflow can have multiple paths that can be taken based on conditional routing. The column in the WSubWork table is SubWork_DateDue_Max.
o pDATEINITIATED 
 Date pDATEINITIATED
The date the sub-workflow was initiated. The column in the WSubWork table is SubWork_DateInitiated.
o pDATECOMPLETED 
 Date pDATECOMPLETED
The date the sub-workflow was completed. The column in the WSubWork table is SubWork_DateCompleted.
o pSTATUS 
 Integer pSTATUS
The status of the sub-workflow. The column in the WSubWork table is SubWork_Status. The possible values for the status are:
WAPI.SUBWORK_STATUS_EXECUTING
WAPI.SUBWORK_STATUS_DONE
o pTITLE 
 String pTITLE
The title of the sub-workflow. The column in the WSubWork table is SubWork_Title.
o pPROJECT 
 String pPROJECT
The project identifier for the sub-workflow. The column in the WSubWork table is SubWork_Project.
o pUSERDATA 
 Dynamic pUSERDATA
Stored data that can be used by the sub-workflow. The column in the WSubWork table is SubWork_UserData.
o pCUSTOMDATA 
 Dynamic pCUSTOMDATA
Stored data that can be used by the sub-workflow. This field is used to store data that is needed for customizations. The column in the WSubWork table is SubWork_CustomData.