DriveWorks Pro 19

Triggered Action

Triggered Action

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:

• An Email can be sent once a model has been generated alerting a Team Leader to a Specification being completed.

Create a Triggered Action

To create a Triggered Action:

Open the Project in DriveWorks Administrator and go to Stage 4: Output Rules then Documents - Data.

1. Click the Add button on the command bar to launch the Create Document Wizard.
2. Select Triggered Action from the Documents List and enter a name in the field under the list.

   

3. Click Finish to close the wizard.
4. The document will open for editing.

   There are 2 items that require values entering:

   • Action - Is the name of the Transition or Operation the Specification will use when the Triggering Files are created.
   • Triggering Files Result - Is the name of a File, created by a prior State, that will trigger the action.
5. Select the Action Rule field and click the Build... button.

   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.

6. Select the Triggering Files Rules field and click the Build... button.

   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.

7. Optionally the States To trigger On can be set. 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:

   Rule	Notes
   "Completed|Released"	DriveWorks Autopilot will not attempet to trigger the Operation or Transition until the specification is in the Released or Completed state.

Tags rule

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.

See Also

Trigger Settings (for Autopilot)