A Triggered Action allows a Specification to Transition to a State once a specified file has been created.
Triggered Actions can only be processed by DriveWorks Autopilot.
Using a Triggered Action allows the default order of generating outputs to be manipulated to better suit your needs.
To create a Triggered Action:
Open the Project in DriveWorks Administrator and go to Stage 4: Output Rules then Documents - Data.
the Action is the name of the Transition or Operation the Specification will use when the Triggering Files are created.
The rule must equal or evaluate to a Transition that exists in the Specification Flow.
|"Manufacturing"||Will place the Specification into the Manufacturing Transition.|
The Triggering Files is the name of a File, created by a prior State, that will trigger the action.
The rule must equal or evaluate to a Full Path and File Name of a file being generated by a prior State.
|"\\DriveWorksData\Files\Housing "&OrderNumberReturn&".slddrw"||The file \\DriveWorksData\Files\Housing 1234.slddrw will trigger the Transition once it is created.|
|DWSpecificationFullPath&"\Housing "&DWSpecification&".slddrw"||The file \\DriveWorksData\Files\Housing 1234.slddrw will trigger the Transition once it is created.|
Enter the name of the Tag that will determine this in the Tags field.
See Tags below for more information.
This field gives greater control on the timing of when the action is triggered.
This specifies the state(s) the specification must be in for the trigger to execute.
Enter the name of the State the Specification must be in before DriveWorks Autopilot attempts to trigger the Operation of Transition given in the Action field.
Multiple State names can be entered by using a pipe-bar delimited list, for example:
|"Completed|Released"||DriveWorks Autopilot will not attempet to trigger the Operation or Transition until the specification is in the Released or Completed state.|
Tags are relevant when two or more DriveWorks Autopilot machines are deployed.
Tags allow control over which DriveWorks Autopilot processes the required information for a specification.
The result of the Tags rule must match a Tag set in DriveWorks Autopilot - Edit Tags.
|If(HighPriorityCheckBox=True,"High","Low")||When the checkbox HighPriority is checked will result in the tag High being applied to the parameter. Otherwise the Tag Low will be applied.|
DriveWorks Tech Tips Portal
Triggered Actions allow DriveWorks to wait until a designated file exists before transitioning a specification.