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 1810

Customer Part Numbers - ShipTo Level

Customer part numbers are not supported by elastic search auto-complete. Customer part number is returned in auto-complete if the product is assigned to a BillTo. However, if the product is assigned to a ShipTo the customer part number is returned...
4 months ago in Customized Commerce / Catalogs 0

Ability to name versions of content

Hello, it would be extremely beneficial to allow content editors to edit the name of versions in the version gadget as well as the locale associated with it. For example, sometimes we make changes to a version that we're not ready to go live with ...
4 months ago in Content Management / Content Manager 0

Support blue/green deployment

As a Customer, I would like to have a blue/green deployment mechanism so that I can confidently implement substantial changes, encompassing both code and content updates, in production. Description I am planning to deploy a new feature to my app t...
about 1 year ago in Optimizely Graph 0

To be able to disable renditions for individual assets in Library

Hi Team, are there any plan to allow renditions to be disabled on an asset-by-asset basis. Maybe as a menu option to turn off ? Reason being that some assets do not require renditions to be created. e.g. logo's ?
about 1 year ago in Content Marketing / DAM/Library 1

@mention multiple users

It'd be nice to be able to @ mention everyone assigned to a step in a workflow of a task. Similar to slack's "[at] here" functionality.
over 1 year ago in Content Marketing / Notifications 1 Future consideration

Incorporate the use of same meaning words (synonyms) for the Library search

Please update search within the Library to return images where the keywords are similar to what is entered. Our employees are searching the Library for words which are similar to, but do not exactly match which has been added as metadata through t...
about 1 year ago in Content Marketing / DAM/Library 0

Persistent notes field on each page

As an Admin/Editor I would like a Persistent notes feature for each page so that I can store page specific information that only editors/admins can see. EG: this page managed by Product Marketing teamEG: do not delete or move this page
9 months ago in Content Management / Editing 0

Full support for CMS language settings

It should be simple to get language behavior consistent with CMS language settings around fallback and replacement languages.
almost 2 years ago in Optimizely Graph 0 Future consideration

Limit the number of workflows/briefs visible to different teams

Currently, every user has access to all active workflows and briefs in Welcome. However, we would like to restrict the visibility of workflows and briefs to specific users or teams. For instance, the content team should only see content-related wo...
over 1 year ago in Content Marketing / Settings + Configuration 0 Future consideration

Deleting Commerce Catalog items warning does not tell you if what you are deleting is referenced anywhere

When you delete a Page or Block in the CMS, a dialog box is shown that informs the user everywhere the items being deleted are referenced. In Commerce Catalog, if you attempt to delete an item you only receive the warning below. It does not inform...
over 3 years ago in Customized Commerce / Catalogs 6 Planned