Trigger Events

Listed below are the available Trigger events that can be used. For more information about how to create a Trigger, refer to the Adding and Maintaining Triggers chapter in this manual.

After Asset Built

If this event is selected, the Trigger will be fired when an asset is finalised after creation from an Asset Builder or Account Manager Page. Finalised assets are assets that have any required metadata values or paint layouts configured. For example, if a user creates a Standard Page asset using an Asset Builder, configuring the information for any required metadata values, this Trigger will be fired.

After Asset Metadata Updated

If this event is selected, the Trigger will be fired when a Metadata Schema for an asset is regenerated, after being updated. For example, if a user changes the Description metadata field for an asset and then regenerates the Metadata Schema, this Trigger will be fired.

After Workflow Approval

If this event is selected, the Trigger will be fired when a user approves the changes to an asset in Workflow. For example, if a user approves the changes that have been made on the Home page, this Trigger will be fired.

After Workflow Rejection

If this event is selected, the Trigger will be fired when a user rejects the changes to an asset in Workflow. For example, if a user rejects the changes that have been made on the Home page, this Trigger will be fired.

Asset Accessed

If this event is selected, the Trigger will be fired when an asset is accessed. For example, when a user views the Home page, this Trigger will be fired.

Asset Attributes Changed

If this event is selected, the Trigger will be fired when the attributes of an asset are changed. For example, if a user changes the name of a Standard Page, this Trigger will be fired. This event will also include assets that cannot be created by a user such as a Bodycopy asset or a division.

Asset Attributes Saved

If this event is selected, the Trigger will be fired when changes to the attributes of an asset are saved. For example, if a user changes the name of a Standard Page, when they click Commit this Trigger will be fired.

Asset Cloned

If this event is selected, the Trigger will be fired when an asset is cloned. For example, if a user uses the Asset Maps Clone function to create a copy of an asset elsewhere in the system. For more information on cloning, refer to the Cloning an Asset chapter in the Concepts manual.

Asset Content Changed

If this event is selected, the Trigger will be fired when the content of an asset is altered. This includes changes to all Content Types, such as the WYSIWYG Editor or Raw HTML etc. Please note that this event will not be triggered by changes to File type assets (e.g. PDF Documents or Images).

Asset Created

If this event is selected, the Trigger will be fired when an asset is created. For example, if a user adds a Standard Page under the Site, this Trigger will be fired.

Asset Lookups Updated

If this event is selected, the Trigger will be fired when the lookups for an asset is updated. For example, if the URL of an asset is changed, or a Design is applied to an asset, this Trigger will be fired.

Asset Metadata Updated

If this event is selected, the Trigger will be fired when a metadata value for an asset is updated. For example, if a user changes the Description metadata field for an asset, this Trigger will be fired.

Asset Recached

If this event is selected, the Trigger will be fired when an asset is recached using the System Clear Cache Suffix. By default, this suffix is _recache. For example, if a user re-populates the cache of a page by appending _recache to the Site URL, this Trigger will be fired.

Asset Updated

If this event is selected, the Trigger will be fired whenever the micro version number of the asset is updated. In other words, when the Commit button is pressed.

Before Asset Created

If this event is selected, the Trigger will be fired just before an asset is created. For example, if a user creates a Standard Page, this Trigger will fired just after they click the Commit button but before the asset is seen in the Asset Map. This can be used, for example, to stop users creating assets in the wrong location of the system.

Before Asset Deleted

If this event is selected, the Trigger will be fired just before an asset is moved to the Trash or deleted. This can be used, for example, to stop users from deleting a user account from the system.

Before Status Changed

If this event is selected, the Trigger will be fired just before an asset's Status is changed. This can be used, for example, to stop users from changing an asset to a particular asset Status.

Before User Logout

If this event is selected, the Trigger will be fired just before the user logs out of the system. This can be used for trigger actions where user details are required. For example, you can use the Send Email trigger action to send an email to the user while they log out.

Link Created

If this event is selected, the Trigger will be fired when an asset is linked within the Asset Map. For example, if you link the Contact Us page under the Home page, this Trigger will be fired.

Link Deleted

If this event is selected, the Trigger will be fired when a link for an asset is deleted. For example, say the Contact Us page has been linked under the Site and Home page. If a user deletes the Contact Us page under the Home page, this Trigger will be fired.

Matrix Cache Cleared

If this event is selected, the Trigger will be fired whenever cache is cleared on a specific asset. Please note that this event is not available on systems using Memcache cache storage or when cache is cleared either system wide or by URL.

Metadata Time

If this event is selected, the Trigger will be fired when the Metadata Triggers Cron Job is run (for more information about this job, refer to the System Management manual).

Order Submitted

If this event is selected, the Trigger will be fired when an order has been created and paid for. Please note that this event will only appear when you have the E-Commerce module installed in your system.

Payment Completed

If this event is selected, the Trigger will be fired when a completed transaction is posted back to the system from a DataCash Payment Gateway transaction. Please note that this event will only appear when you have the E-Commerce module installed in your system.

Paypal IPN Completed

If this event is selected, the Trigger will be fired when a PayPal Instant Payment Notification (IPN) is verified and completed by the system. Please note that this event will only appear when you have the E-Commerce module installed in your system.

Public User Session Created

If this event is selected, the Trigger will be fired when a public user session is created. For example, when a user first accesses the Site, this Trigger will be fired.

Simple Edit Accessed

If this event is selected, the Trigger will be fired when a user views an asset in the Simple Edit Interface. For example, if the user is editing the Home page in the Simple Edit Interface, this Trigger will be fired.

Status Changed

If this event is selected, the Trigger will be fired when the Status of an asset is changed. For example, if a user changes the Status of an asset from Live to Safe Edit, this Trigger will be fired.

User Login

If this event is selected, the Trigger will be fired when a user logs into Squiz Matrix. This includes both the Administration and Simple Edit Interface.

User Logout

If this event is selected, the Trigger will be fired when a user logs out of Squiz Matrix. This includes both the Administration and Simple Edit Interface.

PreviousNext