This tool will delete all Bulkmail Users from the system that match email addresses present in a text file, which is uploaded as part of the tool's interface.
This new Menu Design Area setting ("unwanted_asset_types") lets you set a number of asset type(s) that are excluded from a menu. The types chosen will also exclude all descendant asset types.
The way Paint Layouts work in general has been overhauled quite radically. The "Lookup Values" screen has been renamed "Lookup Settings". The changes to this screen in summary:
When evaluating which Paint Layout asset to display, the following rules apply:
This new trigger action allows you to set an asset-level Paint Layout (both standard and Override) on an asset that fires a trigger. Dynamic parameters can be used to select an alternative asset ID for either one.
Asset-based Paint Layouts can now be set on assets created through an Asset Builder.
This new functionality allows you to pass extra GET variables to an asset being included via Nest Content. The values can include global keywords and keywords of the asset you are nesting (using %nested_asset_*% instead of %asset_*%). These extra keywords will overwrite GET variables passed through a query string, but will only have the lifetime of that nesting.
HTTP GET variables are now available as global keywords using the %globals_get_*% format. Only scalar variables are able to be used as global keywords; arrays are not supported.
The Remote Content asset now accepts global keywords in the URL. Caching of output has changed slightly to better handle the possibility for dynamic URLs.
This is a new "Special Page" option added to Site assets. It is triggered when a user accesses an asset with "Archived" status, without the appropriate read permissions. (Due to it being archived, users actually need write permissions to get read permission too.) The page behaves exactly like the "Not Found" special page option, in that it will return a HTTP 404 status code.
This new command-line script, located in the root of the Bulkmail package, lets you queue up a Bulkmail Job to run immediately. This can be used by a Cron system outside of Matrix to schedule a time to send a Bulkmail Job. Apart from the system root, the script accepts one parameter: the asset ID of the Bulkmail Job to queue. It will only run if it is not already running (ie. status is set to "Under Construction").
This new trigger action will remove either a single metadata schema (if it exists) or all metadata schemas from the asset that fired the trigger.
This option allows you to set a different period for requesting the browser cache the output of a Matrix asset, to the period that Matrix itself caches things using the Cache Manager. Specified in seconds. If omitted or zero (which is the default), these values are the same.
It is now possible to designate certain permissions, workflow schemas and metadata schemas with the ability to not cascade to lower assets, regardless of the normal asset-level "Cascade" setting. When this option is selected, new children of the asset (whether created or linked/moved) will not have those settings cascaded to them. (Workflow schemas and permissions will still cascade to their dependent children, to be consistent with current practices of adding these with cascading to existing assets turned off.)
Two new Trigger Events are now available for Workflow Approval and Workflow Rejection. These events are fired when a workflow is resolved on an asset in the respective way.
The form elements shown in Asset Builder now have a prefix "AB_" to make them XHTML-compliant. Scripts or form submissions relying on these IDs will need to be updated to maintain intended operation.