| |
OScript API/Built-in Package Index |
WAPISUBWORK is the object handle of a sub-workflow. It is used in the WAPI functions for workflow manipulation operations.
Stored data from customization that can be used by the sub-workflow.
The date the sub-workflow was completed.
The maximum possible due date for the sub-workflow.
The minimum possible due date for the sub-workflow.
The date the sub-workflow was initiated.
The ID for the map stored in the WMap table that will be used as the route definition for the sub-workflow.
The project identifier for the sub-workflow.
The subWorkID for the sub-workflow that started this sub-workflow if it was started as a sub-workflow from a task.
The ID for the task that started this sub-workflow if it was started as a sub-workflow from a task.
The status of the sub-workflow.
The unique ID for the sub-workflow.
The title of the sub-workflow.
Stored data that can be used by the sub-workflow.
The unique ID for the workflow.
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.
The project identifier for the sub-workflow. The column in the WSubWork table is SubWork_Project.
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.
The date the sub-workflow was initiated. The column in the WSubWork table is SubWork_DateInitiated.
The status of the sub-workflow. The column in the WSubWork table is SubWork_Status. The possible values for the status are:
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.
The unique ID for the sub-workflow. The column in the WSubWork table is SubWork_SubWorkID.
| Copyright © 2023 OpenText Corporation. All rights reserved. |