MySource Matrix has been superseded by Squiz Matrix. This site will remain available for archival purposes only; it is not intended as a current source of Matrix information. For all the latest on Matrix, including documentation and release information, visit the Squiz Matrix site.
A new option, "Auth Filter", has been added to the LDAP Bridge to restrict the users who are allowed to authenticate by LDAP user attributes. Filter specifications such as "ou=Sydney" (for users within a Sydney office) or boolean combinations "&(ou=Sydney)(ou=Developers)" (Sydney developers) can be specified here.
Some new options are now available for CAPTCHA fields on the "Form Contents" screen in Custom Form. This has been graciously contributed to the Matrix core by Nic Hubbard.
These new options - available from the "Details" screen in Asset Builder and Account Manager, and the "Contents" screen in Custom Form - include the ability to specify a TrueType font from a TTF file, the character angle range and use of arc shapes across the characters. Uppercase letters and numbers are also available as options for CAPTCHA fields.
A date range can now be to be specified in which all search results must fall. This date range is configured from the "Restrict Results Date Range" section of the "Search Fields" screen of the Search Page asset, and uses a standard asset date field as a reference point.
For example, a Search Page can be configured to return assets which have been updated in the last two weeks. The Dynamic Date Range is only a backend feature and as such cannot be configured or included in the Search Page form for user control.
A new command line script, "system_integrity_check_indexes.php", included in the "scripts" directory has been added. This script checks for any missing indexes in the Matrix database.
The SQL statements for any missing indexes are printed for copying and manual intervention. This is a manual process as adding keys automatically may result in SQL errors depending on the current system state, or an unexpected change of tables which were reconfigured for a particular purpose.
This script also checks for unique database indexes. The index definition is also checked on PostGres systems. For example, when Matrix is expecting an index on columns "a", "b" and "c", but the database only has the first two columns indexed, an incorrect index will be reported.
A new switch is provided in the "CAPTCHA" section of the "Details" screen of Account Manager and Asset Builder assets and the "Contents" screen of Custom Form to enable an Accessible CAPTCHA. When enabled, a link will appear next to the CAPTCHA image, whether used in isolation or within a "%form_captcha%", to toggle between using the CAPTCHA image or an email address field.
When clicked, the image CAPTCHA interface will be replaced with a text field and button, prompting for input of the user's email address. A verification email will be sent to the specified address once the "Submit Address" button is clicked. The user's session and the resultant email is populated with a key which is used to match the intention to submit the form to the corresponding user.
A link is provided in the email which when clicked will verify the key against that stored in the session and flag the form as verified for CAPTCHA purposes.
Once the form is submitted, the contents is accepted. The Accessible CAPTCHA process must be restarted for subsequent forms or upon verification failure of fields in the same form, as is the case with the traditional CAPTCHA.
The list of Workflow Steps on the Details screen of Workflow Schema assets now provides a drag-and-drop interface for re-ordering these steps. In order to re-order steps, drag the Step number at the left of each entry, above or below other Step entries. The dragged step will become slightly transparent and provide docking points (similar to re-ordering assets in the Asset Map). Release the mouse button and when the steps are in the desired order, click "Commit" to complete this action.
An "oci:" prefix is now added from the separate fields and recognised when a DSN is manually entered for DB Data Source and DB Connector assets. The DSN supplied can be in simple PDO_OCI format, with a "dbname=" specification.
It is now valid to provide an Oracle connection by one of the following methods:
Please note that the "oci:dbname=" notation is only supported to the point of providing access to an Oracle database and is not designed for or intended to emulate the full PDO_OCI DSN specification for Oracle connections
Pending User accounts are now stripped of any permissions cascaded to them by the Pending Accounts folder. The only permission they will keep by default is its own Admin Permission, as is standard across all users.
Introduced a new "Custom Messages" screen to the Workflow Step asset for entering a custom Workflow message body for a Workflow Step. The following workflow messages can be customised: invitation, approval, rejection, stale workflow, and escalation.