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.
[ Feature Request #4439 ]
A new EES Login Design asset has been added to MySource Matrix to complement the new Easy Edit Suite interface, providing a login page that is visually consistent with the EES's sleek MySource Mini-style design.
When no alternate Login Design has been set for a Site using the Easy Edit Suite, the default MySource Matrix login box will be displayed - styled to resemble the system's Administration interface. The majority of users of the Easy Edit Suite will not be familiar with the Matrix backend, so it is important to provide a smooth user experience by creating a consistent look and feel in all aspects of the EES interface. This is helped achieved using the EES Login Design.
The ees_login_design asset is located in the System Designs Folder, under the System Configuration Folder in the Asset Map. This design can be applied on the Settings screen of the Site you have enabled the Easy Edit Suite for. To do this, select the design in the System Defined Login Design field.
Once the design has been committed, the new Login Design will be used for the Easy Edit Suite's login page on your Site. This login page will be displayed when users who are not logged in attempt to access the /_edit interface.
[ Feature Request #4440 ]
When enabling Roles on a system, users previously only had the option of enabling Roles on the entire system, meaning that Roles for both Permissions and Workflow were enabled.
As Roles can be quite performance intensive, this feature allows users to enable Roles individually for both Permissions and Workflow. This means that if, for example, only Workflow Roles were enabled, the system's performance would not be affected when dealing with Permissions.
These fields are located on the system's System Configuration screen.
[ Feature Request #4449 ]
Previously, the LDAP package only supported the organizationalPerson and intOrgPerson objectClasses for User objects. This feature introduces the userProxy objectClass, allowing User objects using this objectClass to be expanded in the Asset Map. Such Users would have previously been discarded by the system and excluded from the Asset Map's LDAP tree.
[ Feature Request #4446 ]
Enhancements have been made to the JS API's getChildren() function to return NOTICE linked children in the JS API's response. Previously, NOTICE linked children were grouped as Non-Dependant children.
direct_dependant_child => 1 direct_non_dependant_child => 6
This feature enables the JS API to differentiate between these child types, returning values for both Non-Dependant and NOTICE children, as well as for the Dependant children of the asset.
direct_dependant_children => 1 direct_non_dependant_children => 2 direct_notice_linked_children => 4
These enhancements have been added to provide a more comprehensive response from the JS API, assisting in the development of Phase 2 of the Easy Edit Suite.