Triggered Action (DriveWorks Documentation)

Triggered Action

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.

For example:

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

To create a Triggered Action:

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

Click the Add button on the command bar to launch the Create Document Wizard.
Select Triggered Action from the Documents List and enter a name in the field under the list.
Click Finish to close the wizard.
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.
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.

Rule	Notes
"Manufacturing"	Will place the Specification into the Manufacturing Transition.

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.

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 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.

Rule	Meaning
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 Autopilot must be set to process the information being tagged.

DriveWorks Tech Tips Portal

Triggered Actions

Triggered Actions allow DriveWorks to wait until a designated file exists before transitioning a specification.

DriveWorks Tech Tips Portal is available to DriveWorks Pro customers with an active subscription and support contract.

Tech Tips provide cut down projects that highlight specific functionality for faster and more effective learning.

To access the portal:

The portal provides a search facility, start typing the name of the Tech Tip (as indicated above) to display the Tip you require.