422 results found
-
Re-work or re-name the Send Back feature
"Send Back" is an ambiguous term which could just as easily mean "return to the person who assigned this to me" as it does "undo all of this step's actions and set it to the last step". Can this feature be reviewed and tweaked so it works properly, or be renamed to explicitly describe what it does?
Currently, we are seeing users assume that they are returning a completed step to the owner and selecting "Send Back" and it's undoing everyone else's work on the sub-steps associated with that step, which is hugely disruptive!!
1 vote -
View out of office in convert screen
It would be super helpful to be able to see someone's out of office (the red exclamation or something similar) while in the conversion screen (converting from request to task).
1 vote -
CMP: Multiple Assignees for Tasks
Allow more than one person to be assigned to a task (currently limited to 1 person or 1 team). This flexibility, already available in Requests, would help manage collaborative work more effectively.
1 vote -
CMP: Campaign Template – Task Duration
In Campaign templates, display task duration alongside dates. Updating the dates should automatically adjust the duration, and updating the duration should automatically adjust the dates, keeping schedules consistent and easier to manage.
1 vote -
SLA Fields by Template
Add SLA fields preset by template type. For example, a Website request template could have an SLA of 5 days that automatically appears on the form (read-only for users). The system would also automatically close tickets after a set period (e.g., 2 weeks) if there’s no follow-up from the requester.
1 vote -
Hyperlinks in Free Text Fields
Enable URL links / hyperlinking in standard free text fields on forms. Currently, hyperlinks work only in updates or rich text fields, but not in regular free text, limiting flexibility for adding references or resources.
1 vote -
Template UX/UI Improvement
Allow template descriptions to appear at the top of the request form rather than after the request description. This improves form flow and makes it easier for users to understand the context before filling in details.
1 vote -
Enhanced Template Logic
Improve conditional logic in request templates. Currently, options are limited to “jump” or “show,” but we need more advanced conditions (e.g., “if X, show Y, then jump/proceed to Z”) to design templates more effectively and handle complex workflows.
1 vote -
Context on Request Fields
When raising a request, allow hover-over context/tooltips for field selections so users can see guidance without needing helper text inside the field. Currently, the value only shows on the template and not at the next selection level, which can cause confusion.
1 vote -
Automated Assignee for Time Off
Allow automatic reassignment of tasks when a user logs time off, so assignees are temporarily replaced and work continues without manual updates.
1 vote -
Add a “Requests by Assignee” view to dashboards
Add a “Requests by Assignee” view to dashboards, showing who is assigned or approving each request, rather than who raised it. This helps track ownership and progress more effectively.
2 votes -
Add a save drafts / auto-save feature
Add a save drafts / auto-save feature in the Request module and comment fields, so users don’t lose updates or notes if they can’t complete them in one go. Currently, auto-refreshes can cause comments to disappear, so this would prevent data loss.
1 vote -
Improve CMP Task Experience with asset Expiry Date & DAM Notification
Background / Current Behavior:
The customer has reported that within CMP tasks, there is no trigger or notice to add the expiry date before completing the task. Additionally, there is no pop-up message indicating that the asset will not be sent to the DAM. This can lead to confusion and a poor customer experience.Requested Improvement / Feature:
Introduce a clear trigger or notice within the CMP task to prompt users to add the expiry date before completion.
Implement a pop-up message to alert users when an asset will not be sent to the DAM.Customer Impact:
Without these prompts,…2 votes -
Enable editing of key fields directly within the Plan module, including fields such as Depends On, Status, and Cur
Currently, these fields cannot be edited inline and require opening each individual item. This slows down workflow management and makes bulk updates or quick adjustments inefficient. Allowing inline editing would improve usability, speed up resourcing and timeline changes, and reduce administrative effort when managing multiple tasks.
2 votes -
Support link in navigation on CMP
I have raised a few support tickets and whilst it is easy to do that via the navigation, it it not possible to quickly get to the support portal to see how the tickets have progressed. It would be good in the navigation, or in the Customer Support 'Contact us' pop-up, to have a link to the support portal.
1 vote -
Add Review Option to Submitted Work Requests
Currently, when a user submits a request, the only available actions are Accept or Decline. This creates a gap in the workflow because there is no way to indicate that a request has been accepted but is still being evaluated or queued for setup.
We need an additional status, such as “Review” or “In Review,” that can be applied after a request is submitted. This status should be visible to both internal users and the requestor, so the requestor understands that their submission is actively being reviewed and has not been ignored.
From an internal workflow perspective, this status would…
2 votes -
Value Name with Field Id
Currently, the CMP asset response returns only the value IDs inside the Values array. The response structure should be updated to return a collection of objects, where each object includes both the ValueId and the corresponding ValueName.
"Fields": [
{
"Name": "GEOGRAPHY",
"Values": [
"d26e76eed40611f0a979d6dd850eab0790",
"37b86280d40711df0afc59a90521e39d3",
"d26d00ded40611f0a97d9d6850eab0790"
],1 vote -
Name and ID
CMP Graph.
We need to combine CMP assets results with Episerver search items. However, due to an issue in the CMP result set, the filter Id and Name values are coming in separate arrays, and the values do not align correctly.
Currently, the facets response returns only the Name and Count fields. The Id field should also be included in the CMP facet filters response so that each facet value can be uniquely identified.
The facet name counts are not consistent. When we apply a WHERE clause filter, the facet counts change unexpectedly. The facet name counts should remain consistent…
2 votes -
fiscal
Fiscal year vs. Calendar Year
I know we can create custom views but it would be ideal under the Organization's Business Calendar to change to a fiscal calendar so that when we share views based on quarters, it aligns with how our company operates, i.e. our Q2 is Jan-Mar, not April-Jun.
1 vote -
Restrict Workflow usage
You should be able to restrict usage of Workflows to certain Assets, or to certain Teams/Users (or, ideally, a combination of both).
We have certain assets which need to go through specific approval flows for compliance reasons and currently the platform has no way to restrict who can do this, or whether the Asset can be put through different workflows accidentally.
1 vote
- Don't see your idea?