Last Updated: 17 Oct 2016

The Batching screen of the Trigger Manager allows you to execute the Triggers on a section of your system as if a Trigger Event had occurred. It is ideally used when you have set up a new Trigger to perform a certain action but you would like to perform this action on an existing set of assets.

For example, if you have just created a Trigger to create different image varieties when an Image asset is created, you can force the Trigger to fire and create these varieties for the existing Images.

To force a Trigger to fire, fill in the following fields:

  • Target IDs: select the Trigger(s) that will be executed when the specified event(s) is replicated. If this field is left blank, all applicable Triggers will be run. To select further Trigger, click the More... button - additional fields will appear on the screen.
  • Target Asset: select a specific asset or root node section of your system that you want to fire the Trigger(s) on. This allows you to restrict the firing of Triggers to a specified asset, for example, a particular Site.
  • Children: checking this field will include all child assets of the specified Target Asset when defining the section of the system to fire the Trigger(s) on.
  • Events: select the Trigger Events that you want to replicate the occurrence of, firing any applicable Triggers specified in the Target IDs field. For example, if you want to execute a Trigger that is configured to fire when an asset is created or when its Status is changed, you would select the Asset Created and Status Changed events in this field.

Once you have entered the required information, click Commit; the designated Trigger(s) (as defined in the Target IDs field) that are 'listening' for the selected Trigger Events will fire on the assets specified in the Target Asset field.

Previous Finish

Previous Chapter