Delayed Ticket Start
- Last UpdatedApr 24, 2025
- 1 minute read
When the Delayed Ticket Start action is used, a ticket is cut, the active batch becomes completed, and the next pending batch (if one exists) is started after applying a delay.
Note: This action is useful only when “Batch Switch on Manual Ticket Start” is configured for the Batch Transfer record. For more information, refer to the AVEVA Pipeline Operations for Liquids Administrator Guide documentation.
|
Action |
Type |
Optional |
Output |
Description |
|---|---|---|---|---|
|
batchTransferName |
String |
False |
False |
This input parameter specifies the name of the Batch Transfer record. |
|
Action |
String |
False |
False |
This input parameter specifies the action, it should be: “DELAYED TICKET START”. |
|
arguments |
String |
False |
False |
This input parameter is ignored, it should be: “” |
|
Success |
Boolean |
False |
True |
This output parameter will indicate whether the action was successful, when successful “success == True”. |
|
returnMessage |
String |
False |
True |
When “success == False”, this output parameter will provide a insightful message for the unsuccessful action. |
|
User |
String |
True |
False |
This optional input parameter specifies the name of the user to use when generating events for this action. If not specified, then the default is: ”unknown_user”. |
|
Location |
String |
True |
False |
This optional input parameter specifies the name of the location to use when generating events for this action. If not specified, then the default is: “unknown_location”. |