Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

All feedback

Showing 1583 of 1583

Limitation of number of sent forms

A customer, managed by Natalia Butor, needs to limit the number of sent forms. When googling I found a suggestion for using a criterion that uses the Forms API to count the number of sent forms. Then using a visitor group that hides the form when ...
about 2 years ago in Content Management / Forms 1

Async client side custom validators in Epiforms

Custom validators for Epiforms must currently return their validation result synchronously, this limits the kind of validation to simple string checking. In scenarios where a server must be consulted to check an input value it is often a better ex...
about 2 years ago in Content Management / Forms 0

More Descriptive Notification Messaging

Currently, when changes are made to work requests, for example changing the priority level, etc., the notification message just reads ‘The requester has made changes to the request….’ If it could be changed to something with more description/infor...
about 2 years ago in Content Marketing / Notifications 0 Future consideration

Improve IContent API:s to support bulk actions

Background CMS heavily relies on CRUD operations for IContent. And therefore there are Content Events for single item operations. And then subscribing tasks such as Search&Navigation Indexing and other event subscribers also reacts on every in...
over 2 years ago in Content Management / Technical 0

Feature Flag Lifecylcle Analytics

One of my goals as an administrator of feature flags is to understand the lifecycle of our feature flags. When it was created and the various data points for it's rollout. I struggle to maintain the lifespan of our flags without alot of manual work.
over 2 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

Support to edit link name in Insert/Edit link dialogue TinyMCE

Editor can only change the link title through the dialogue, however most of the editors would like to change the name instead as it is the actual content displaying to customers. there is no easy way to change the link name without going to source...
over 2 years ago in Content Management / Editing 0

Built-in support for SAML2

SAML2 is a popular protocol for federating users and roles from an enterprise identity store to enable SSO. It would be very helpful if it was possible to setup a trust relationship to a SAML2 IdP either through simple configuration or ideally usi...
over 2 years ago in Content Management / Roles and Security 0 Will not implement

Create dashboard that tracks the number of customers that have activated their accounts per week/month

Original request from Brady Industries. Brady has recently created new commerce accounts for their customers, and they would like to track which customers have logged in and activated those accounts. Specifically, they would like a dashboard that ...
over 2 years ago in Commerce Analytics 1 Planned

On-page comparison tool improvement

When comparing a submitted version of a page to the published version of a page, it would be helpful to have an indication of what content has been added, edited, or deleted. Currently we need to eyeball it to see what the submitter has changed an...
about 3 years ago in Content Management / Collaboration & Approval 0

Set Visitor Group by Subsite

Admins shoudl have the ability to filter or set specific Visitor Groups to be availabe in admin based on subsite. Having all VG available to all users for all subsites does not allow smaller groups to access a subset for ease of use and optimization.
about 3 years ago in Content Management / Content Manager 0