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

Allow experimentation for email trigger campaigns

As a marketer I want to test different triggers and different prioritization against each other and get reports about scenario A and B. For this I'd like to set up an independet set of triggers (set B) with prioritisations and select a %, a set of...
over 3 years ago in Product Recommendations / Email Personalization / Experimentation 0 Future consideration

Improved Workflow Approvals

As a content editor I require parallel approval workflows and the ability to define workflows where I can e.g. skip an approver if needed, providing more detail on the reason for skipping. This will improve my effectiveness as currently we rely on...
over 3 years ago in Content Management / Collaboration & Approval 0

Audit Content

As a group of content management users we have a number of needs to audit our content including the abilities to: Assign review groups of users to pages Assign a review date and frequency of review Email alerts Reminder emails Report of overdue to...
over 3 years ago in Content Management / Content Manager 0 Future consideration

Statistics API for Find

Statistics, for example, most frequent searched keywords should be exposed via an easy to use API. Reported from https://world.episerver.com/forum/developer-forum/Feature-requests/Thread-Container/2015/6/possible-to-get-information-about-most-freq...
over 3 years ago in Search & Navigation 0 Future consideration

Add Async/Await APIs to avoid thread pool exhaustion

Multiple interfaces within the product are forcing clients and partners to abandon proper async/await implementations because the product does not implement async itself. This means that even if solutions properly implement async, they will eventu...
over 3 years ago in Search & Navigation 0 Future consideration

Audit change for the "Visible to" Permissions

Currently, it's not possible to know who is changing permissions to the "Visible to" It's standard to be able to monitor changes made to areas that handle permissions. Could you please add this to the change log?
over 3 years ago in Content Management / Roles and Security 1

Move the EPiServer.DataAbstraction.Activities.Internal.IActivityTypeRegistry to public API

Move the EPiServer.DataAbstraction.Activities.Internal.IActivityTypeRegistry to public API as we needed it when creating custom activities to be able to register those (yes we can now, but the Internal namespace indicates to us that this could cha...
over 3 years ago in Content Management / Technical 0

More Granular Access Rights Assignment

Local editors should be able to edit some pages and without direct root (admin) access. Access rights need to dictate the following for a role which languages and site areas the role has access to and what editing rights.
over 3 years ago in Content Management / Roles and Security 1 Investigating

Archive old projects automatically

Automatically archive projects that have not been used for a certain amount of time.
over 3 years ago in Content Management / Collaboration & Approval 0 Future consideration

Support SVG

Support SVG's. E.g. https://world.episerver.com/blogs/Ben-McKernan/Dates/2015/7/supporting-svg-images/
over 3 years ago in Content Management / Technical 1 Future consideration