Site Search
Content Tools
Main Content
Technical Specifications (CMS)
This category contains technical specifications that relate to assets within the MySource Matrix CMS package (eg. asset listing, asset builder, custom form etc).
Excluding Assets From Asset Listing (Draft)
This document proposes a way to exclude an individual asset from an asset listing.
Asset Listing Position Setting (Draft)
This document proposes a new functionality for the Asset Listing Page which will print selected assets on specific positions on every listing page.
New Form Keyword: Question Note (Complete)
This document proposes a new keyword for the Form's thank you bodycopy which will print the question's note.
Sliding Page List in Asset Listing (Draft)
This document proposes a new keyword that will print sliding list of pages.
Activation Escalation for Pending Accounts (Complete)
This development will allow for actions to be taken when a user created through an Account Manager, that requires email activation, remains unactivated for a certain period of time. Such actions may include the re-sending of the activation email, or the deletion of the account.
Remote Content Page Tag Filtering (Complete)
This document proposed a new filtering option for the Remote Content Page. New filtering option will allow remote content to filter or replace specific tags from the remote content.
Site Map - Formating for Asset Types (Complete)
This document proposes a new option for Site Map asset to specify display formats for different asset types.
Listing LDAP Users with Listing Engine (Draft)
This document proposes a way to list LDAP users in Listing Engine assets and allow users to use keywords to retrieve LDAP user information.
Multiple Page Asset for MySource Matrix (Released)
This document proposes a new Asset for Mysource Matrix, which will provide a way of maintaining and displaying multiple pages of content, whilst still maintaining control over their functionality. The parent will be able to keep track of the pages it has, providing the ability to print page numbers, tables of contents and a standard format across all pages. Each page will be individually accessible and indexable, as each will have their own web paths, yet their display will always be controlled by the parent asset.
Adding metadata values through asset builder (Draft)
This document proposes a way that the asset builder can be extended in order to make it possible to specify values for metadata fields when creating an asset on the frontend.