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

Error in OOTB P21:07 - Order History Step 2 SQL

I've noticed an error in the OOTB sql script for the Order History - Order Detail job step. Navigate to the following link and review the WHERE clause. The final statement has oh.date_last_modified twice and I believe one of these should be ol.dat...
about 2 years ago in Configured Commerce / Orders & Payment 0 Investigating

Simply Field Addition on Task

There are too many steps in order to search for the individual labels at task creation: I want to select two labels for a task that fall in two fields, I have to do the following: Open Fields chevron drop down arrow Click “Add Field” button Scroll...
about 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Filter 'My Tasks' Panel by 'Created by Me'

Task creators are responsible for ensuring tasks do not become overdue, not task assignees. This means that task creators need a quick and easy way to be able to see tasks that they have created specifically in the My Tasks panel (from top navigat...
about 2 years ago in Content Marketing / Miscellaneous 0 Future consideration

Password expiration settings

Right now, in the admin console there isn't the possibility to set password expiration rules. For example, password should expire every 30 hours/days/weeks and the new password shouldn't be like any previous one. It would be great if these setting...
about 2 years ago in Configured Commerce / Users, Permissions & Security 1 Investigating

Restrict the usage of EPiServer.Marketing.Testing add on

We would like to deny the create A/B test access for specific users having publish access.
about 2 years ago in Content Management / Technical 0

Add possibility to define Variations directly within a Rule

Currently, Variations are created separately. It should be similar to Page targeting settings in Web, which also can be defined separately and reused, OR defined directly in the experiment
about 2 years ago in Feature Experimentation / Experiment Authoring 1 Future consideration

On any listing page there should be sorting options

No description provided
about 2 years ago in Feature Experimentation 1 Future consideration

On the Results page, the Name of the Flag that an experiment is based on should be displayed

Currently, only the "Rule key" is displayed, not the Flag name or key. The Rule keycan include the name (/key) of the Flag, but it doesn't have to. So especially when having multiple Results pages open side by side, it's very difficult to distingu...
about 2 years ago in Feature Experimentation 1 Future consideration

Ability of configuring additional wait time between each job steps

Currently there is no provision in OOTB "SXe 07: Order History" sync-up job to let the job finish its first step( i.e. "Order Header") completely at database level before processing the next step( i.e. "Order Lines"). As we observed that OOTB job ...
over 2 years ago in Configured Commerce / Integration 0

Make Campaign Start and End Date Mandatory

We would like a setting at the admin level that would enforce the user to have to provide those dates at the Campaign creation level. Ideally, if the user does not fill them in and clicks “create”, it won’t let the user create the campaign and hig...
over 2 years ago in Content Marketing / Settings + Configuration 0 Future consideration