A Triggered Action allows a specification to transition to a State once a specified file has been created.

Using a Triggered Action allows the default order of generating outputs to be manipulated to better suit your needs.
For example:
To create a Triggered Action:
Open the project in DriveWorks Administrator and go to Stage 4: Output Rules> Documents

There are 2 items that require values entering:
The rule must equal or evaluate to a Transition that exists in the Specification Flow.

Example Rule
| Rule | Notes |
|---|---|
| "Manufacturing" | Will place the specification into the Manufacturing transition. |
The rule must equal or evaluate to a Full Path and File Name of a file being generated by a prior State.

Example Rule
| Rule | Notes |
|---|---|
| "\\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. |
See also
Autopilot - Triggered Actions