Squiz DXP

It would be great to be able to build out a form segment and call it in to a form as required. For example, we have forms where the user may need to add in the details of family members. For each family member there are a number of fields - name, date of birth, phone number, address etc After adding in the first family member user can choose to 'Add another family member'. At this point we'd like to be able to use conditional logic and simple call in the same fields that were used for family member 1. At the moment this isn't possible, so we need to build out the whole section again... and again... and again... This type of functionality has many use cases, could be used for any situation where conditional logic is applied and user has the option to add more information to the form. Some of the forms we are building have theoretically no cap on the amount of extras a user may want to supply. Manually building out a static amount that are only used if conditional logic is triggered is time consuming and makes forms in the system incredibly long and complicated. I see this working as building a form for, in this example all the fields required to collect information about 'family members' and then using conditional logic to call that form into the main form as required. E.g. If user selects 'Yes' to add a family member, call in the 'family members' form.

It would be very helpful to have a "code" form field available in the "Advanced form fields" section. It would also be very helpful to be able to reference one or more CSS files for each form, not just a single CSS file for all forms, as is currently the case through the "Global CSS" setting in the "Form Settings" section of the "Organisational Settings" area of Advanced Forms. Both of these features could be restricted to users with "Forms Admin" privileges.

Request a feature that enables editors to perform a pre-publishing content audit by pressing an "Audit" button. The tool will identify and flag potential content issues to ensure published pages are high-quality, accessible, and error-free. This will streamline the quality assurance process and reduce post-publishing corrections. Benefits *Improves the quality and accessibility of website content. *Reduces manual error-checking time for editors. *Prevents post-publication corrections that disrupt user experience. *Encourages compliance with accessibility and content standards. Request: Trigger: The content editor clicks an 'audit button' in preview mode to check for issues before setting the page live. Content Analysis: The system scans the draft page for the following issues: *Broken Internal Links: Checks for broken internal links to prevent navigation issues. *Broken External Links: Validates external URLs to ensure they are active and functional. *Heading Structure: Reviews headings (H1, H2, H3, etc.) to ensure logical order and hierarchy compliance. *Image Alternative Text: Confirms that alt text is provided for all images. *Spelling Errors: Flags spelling mistakes for correction. *Strange Formatting Code: Detects and highlights unnecessary code introduced when content is copied and pasted from platforms like SharePoint or Word. Generate Audit Report: The system displays an audit summary listing issues detected, categorised by severity and with suggested fixes. Correction Phase: The editor reviews and addresses flagged issues directly in Squiz. Re-audit (Optional): The editor can re-run the audit after corrections to verify fixes.

We are facing difficulties as we get more editors copying and pasting content from Word documents which include unclean, excess code. Other CMSes and even Dreamweaver had this fence at the top of the cliff, but Squiz Matrix is forcing us to use an ambulance at the bottom. Surely not best UX. Can we please get this feature added to the WYSIWYG?

We have situations at the moment where we are developing larger restructures to paint layouts, while metadata updates/additions are made to sections. These changes are often too large to leave in safe edit for a long time, as it will block any changes needed outside of this. Currently, you can set a paint layout to safe edit, and allow drafting changes to pages before it gets published and made live. Would love if we could go a step further. Have paint layout changes come under the same protections that Content and Metadata do while in safe-edit — so we could easily test out swapping to new layouts on live content and let our editors preview them before publishing.

Feature requests for 6.22+ Currently the interface has a number of Help links available in a menu from the ?link: Help Center Documentation Release notes Available asset types Now we’re all using a similar ‘admin’ interface: FEATURE REQUEST: It’d be useful to be able to add a custom link (custom link text, custom URL) at the bottom of the Help list to take the user to in-house Help content on our intranet. Providing in-house links is proving +++useful in Custom Container picker, and providing easy access to our custom content ‘globally’ would be equally helpful. It’s also somewhat compensating for the loss of Edit+. Something in System configuration? Global preferences? -- FEATURE REQUEST: Adding to the above, it’s be useful to change the Help links displayed, depending on the account type of the user logged in. For example, making Available asset types, and probably Release notes, available to a Content editor doesn’t seem useful. A Content Editor doesn’t have, and never will have, access to all the asset types, and for a client on an annual update cycle, showing things they cannot (yet) have in Release notes seems equally unhelpful. Arguably displaying Content Editor help links to a Sys Admin is equally unhelpful. This second feature request is far less important than the first one.

Please consider, we need to test email, and/or any other outbound communications, in our Dev environment. For now, we confirmed with Squiz product team, there will be no outbound email from Dev environment, by over-writing sender address. But, by doing this way, we can't test any Emails and/or any other outbound communications, e.g. email template. If there is a Dev mailbox, will trap all dev emails, it will be good for thoroughly test end to end development.

User story: As a web editor, I need to change list type attributes to ensure policies display the correct list type (see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ol#attributes ) Issue/Opportunity: It is not possible to change list type attribute in the Matrix wysiwg editor. Changling list type requires using the source code editor, and the new list types do not render in the wysiwg view. Request: Support all HTML list type attribute values in the wysiwg editor, including choosing which type to use, and rendering this correctly in the wysiwyg editor.

When a customer saves and submits form, they are issued a link to return to the form. The link when emailed does work and takes customer back to where they were on the form. However, it does not take the customer back to the website where the form has been embedded. Ideally would like this as it does look a little suspicious that where they have been taken back to is not the same site as when they started the form. The email address the link the customer is sent to seems like it can't be changed from the DXP email address. We would like to be able to send this email from the same email address we have arranged the auto reply to come from.

Customize Form can export the submission as CSV. But it is not enough. As more and more people asking for PowerBI, and other data ETL tools. I think instead of providing plugins for different platforms, Squiz can provide a unified Data ETL protocol and interface for on a slave server.