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 1641 of 1641

Automatic copy of database from production to preproduction

Preproduction should resemble production. There should be an automatic function for copying the database from production to preproduction and keep the correct hostnames in preproduction. This should also be possible to schedule as preferred.
8 months ago in DXP Cloud Platform / Data management 0 Future consideration

Daily Digest of Work to cut down on notifications

It would be great if we could choose to receive either a daily or weekly digest of the work and activity in the system that members of the team are associated with. Something like this would cut down on the number of notifications we receive on a ...
8 months ago in Content Marketing / Notifications 0 Future consideration

Request to configure- Avg Available Memory, Avg Http Request executionTime and Avg. process I/O rate for Western Power

Hi Team, We are working with Western Power, Australia. We need a help to configure- Avg Available Memory, Avg Http Request execution Time and Avg. process I/O rate for Western Power Application Insights (all environments). This is required to moni...
8 months ago in DXP Cloud Platform / Health reporting 0 Future consideration

Rewrite CustomerContext to a service with interface

I would be happy to see the CustomerContext class turned into a class with an interface, and no usage of the CustomerContext.Current singleton. This way it can be overwritten or intercepted for customization. In the same way, the logic of Mediacha...
over 1 year ago in Customized Commerce / Customer Services 1 Future consideration

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

Ability to @ mention watchers

It would be great if @watchers was a functional way to notify watchers of a task that there is a comment for them - especially useful when there are a large number of folks that need communicating to.
over 1 year ago in Content Marketing / Notifications / Tasks, Campaigns, and Events 1 Future consideration

Settings - Configure Workflows for Task vs Hypothesis

No description provided

Automated alert on the scheduler container (Linux).

Automated alert on the scheduler container (Linux). it seems not practical we have to check it every day. It will be great if they have alerts on container crashing/being not reachable similar to the ones for the website instance where Optimizely ...
over 1 year ago in DXP Cloud Platform / Infrastructure mgmt. 0 Future consideration

Required Fields on Events

We'd like to ensure our events are tagged as thoroughly as our tasks and campaigns, but there's no way to set up required fields today.
almost 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Allow for Search Stemming

There is no way to create stemming attributes for search. Meaning: if I want to return results for the word "accounting" but not "account", I cannot create a way to use the full term of "accounting". Other examples include ability to restrict sear...
over 1 year ago in Configured Commerce / Search 1 Gathering interest