• |
For a list of available actions, see What is a custom workflow action? . Custom workflow actions are defined in the CustomWorkflowActions.xml file as follows:
The PreActions and PostActions are defined as follows:
Each phase may contain one or more actions with the following properties:
Instructs the service to stop all processing for the current object when an error occurs. |
The properties are defined as follows:
Each action also contains the following nodes:
A list of conditions which determine whether or not to process the action. |
The nodes are defined as follows:
Parameters and conditions support the following predefined tags:
The full path of the current object in the version control system. | |
The version control status for the current object. See Status values for more information. | |
The version control sub status for the current object.See Sub status values for more information. | |
The possible values of a registered object's sub status include the following:
The possible values of a version controlled object’s status include the following:
Each condition node has the following properties:
The type of operations available depends on the DataType property.
The following DataTypes are available:
The following operations are available for a String DataType:
Determines whether or not Value1 and Value2 have the same value. | |
Determines whether or not Value1 does not start with Value2. | |
The following operations are available for a Guid DataType:
Determines whether or not Value1 and Value2 have the same value. | |
The following operations are available for a Version DataType:
The available logical operators include:
To use a logical “And” or “Or” operator, specify a new Condition with only the Operator property.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center