Trigger Events

Last Updated: 11 Apr 2018

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.

Bookmarks

After Asset Attributes Updated

This event will fire the Trigger after an asset's Attributes have been updated. For example, after the name of a Standard Page has been updated.

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.

After Asset Content Updated

This event will fire the Trigger after an asset's contents have been updated. For example, after the Summary or Description of a News Item have been updated. It will also fire on Standard Page assets when the content on any of its Content Containers is updated. Please note that this event will not be triggered by changes to File type assets (e.g. PDF Documents or Images).

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.

After Permission Updated

This event will fire the Trigger after an asset's Permissions have been updated. For example, after Read Access has been applied to an asset.

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

After User Logs In

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.

After User Logs In via Oauth2

If this event is selected, the Trigger will be fired when a user logs into Squiz Matrix via an Oauth2 Account Manager. For more information, refer to the OAuth2 manual.

After User Logs In via SAML

If this event is selected, the Trigger will be fired when a user logs into Squiz Matrix via a SAML Account Manager. For more information, refer to the SAML manual.

After User Logs Out

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.

After Web Paths Updated

This event will fire the Trigger after the Web Paths of an asset have been updated.

After Workflow Approval

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

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.

After Workflow Step Condition Approved

If this event is selected, the Trigger will be fired when all of the conditions on a Workflow Step are approved. For example, if a user approves the changes made to the asset in Workflow and the Workflow Step is complete, this Trigger will be fired.

Asset Accessed

If this event is selected, the Trigger will be fired when an asset is accessed via URL. For example, when a user views the Home page. The Trigger will NOT fire if an asset is used via nested content or the %globals_asset_contents% keyword.

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

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.

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 when asset specific data is updated. These updates include:

  • Generic asset data, such as an asset's status, name, short name, languages, force_secure etc. (updates to the sq_ast table).
  • Asset type specific data, i.e. asset attributes available on the Details screen, as well as other asset type screens (parameter maps, search fields, etc.).
  • Asset metadata values (updates to the sq_ast_mdata_val table).

Please note that updates like permission changes, workflow/metadata schema changes, roles, webpaths, paint layouts, simple edit layouts and designs etc. will not fire the Asset Updated event.

Before Asset Attributes Updated

This event will fire the Trigger before an asset's Attributes are updated. For example, before the name of a Standard Page gets updated.

Before Asset Content Updated

This event will fire the Trigger before an asset's contents are updated. For example, before the Summary or Description of a News Item get updated. It will also fire on Standard Page assets when the content on any of its Content Containers is updated. Please note that this event will not be triggered by changes to File type assets (e.g. PDF Documents or Images).

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 Asset Metadata Updated

If this event is selected, the Trigger will be fired before the Metadata of an asset is updated. For example, before a user changes a text metadata field of an asset.

Before Permission Updated

This event will fire the Trigger before an asset's Permissions are updated. For example, before Read Access is applied to an asset.

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 Logs Out

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.

Before Web Paths Updated

This event will fire the Trigger before the Web Paths of an asset are updated.

Counter Number Issued

If this event is selected, the Trigger will be fired when a counter integer value is issued via the Issue Counter Values trigger action. For more information, refer to the Trigger Actions chapter in this manual.

Form Submission Completed

If this event is selected, the Trigger will be fired when a form submission is completed and submitted. For more information on creating a form, refer to the Custom Form manual.

Form Submission Created

If this event is selected, the Trigger will be fired when a form submission is first created, after the user's answers to the questions on the initial form page have been populated. This event will fire irrespective of whether or not the submission is logged or not. For more information on creating a form, refer to the Custom Form manual.

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.

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.

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.

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.

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.

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.

REST Response Received

If this event is selected, the Trigger will be fired when a response is received from a REST Resource on the Squiz Matrix system (i.e. a REST Resource asset or Call REST Resource trigger action etc.).

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.


Previous Chapter Next Chapter

The Latest

Let Us Know What You Think

Let us know if you spot any errors or if you have any ideas on how we can improve the Matrix Community Website.

Contact Squiz for Demo

Let us show you the true power of Squiz Matrix by giving you a personalised demonstration.