538 results found
-
GUID Indicator in Task History and Versioning
We need to be able to quickly identify when the first version of an asset is being brought in from the Library or uploaded directly from a user's computer. Having that information available to easily view in the task history as well as in the Proofing window would be immensely useful information.
1 vote -
CMP drafting content with different font colours
When copy is drafted in the comments section, we cant change the font colour, but if we past text from MS word that has colour, then CMP picks it up. A longer workaround to get the same outcome. It would be great to just have a colour selection feature
1 vote -
When tagging users I want the name to appear in a different colour
When a user is tagged, it would be nice if that user's name changes to a blue font (indicating a link) which is common with other platforms that have a tagging feature.
1 vote -
Adjusting the size of the tools in Proofing & Versioning
I'm a Proofreader/Editor. When in Proofing & Versioning, the view of my document is teeny tiny because I cannot minimize or resize the Comment section/list on the right side. When I resize my browser window to do a split screen, the only thing that gets smaller is the actual document, nothing else. This is really adding a lot of extra time to my review process. I'm not able to see all the tools at the top because I can't adjust any view sizes. See screenshot.
1 vote -
Globally configure Campaigns as list views
Be able to configure List views particularly what people see when you click a campaign name at a global level.
At the moment, I've been told that, "List Views are user-specific, meaning individual users can customize which columns they see. While there is no global config to "lock" this view for everyone simultaneously".
Since clicking a campaign is such a fundamental thing in Optimizely it's not the same as creating your own list view, this should be configurable globally as to how campaign views appear.
1 vote -
Ability to copy a work request as a template (regardless of status)
Its time consuming to have to complete the same fields in the same form from scratch everytime, for recurrent similar tasks.
I want to be able to copy pervious work requests (regardless of status) to be used as a template to avoid duplicating field completion. I can see a "copy" button on WR's until the point they are accepted, then it disappears. I want to be able to do this on any WR regardless of their status.
6 votes -
Campaign templates need true post‑creation flexibility for admins
There was a previous idea about editing campaign templates that’s marked as Released — but as a current user, the flexibility still isn’t really there.
Once a template is created, most key settings are effectively locked. Even as an admin and the original template owner, things like sharing and user access are read‑only.
The suggested workaround (create a dummy campaign, change sharing, save as a new template, delete the old one) doesn’t scale and creates unnecessary admin overhead.
Templates are meant to be long‑lived and reusable. As teams and access needs change, admins should be able to edit templates directly,…2 votes -
Allow skip of tasks and campaigns
I see you can skip workflow tasks but being able ti 'skip' or 'dismiss' tasks or campiagns would be really helpful. For example, we have very complex campaigns for product launches that include several nested sub-campaigns and tasks that we would want to 'skip' or 'dismiss' for certain product launches.
1 vote -
Efficiency Dashboards: Ability to Filter by 'Steps'
Filtering workflow 'steps' on an efficiency dashboard so we can omit certain workflow steps from the efficiency dashboard chart.
For example, if I set up a 'step bottlenecks' chart, it would be great to be able to filter by Step (is, not, is one of, is not one of). There are certain steps when spread out among many assignees, they start to clutter the chart.
7 votes -
Mandating fields in CPN and TSK templates
Admin to be able to mandate fields while creating CPN or TSK template so Creator must submit requested information or make the drop-down selection before creating CPN or TSK record.
This is required for the filters and search on the platform - to be able to extract records based on fields' entries.1 vote -
Make it possible to save different pieces of content in the same task to unique DAM locations.
We often add design elements to a task that will result in a new piece of content being created. The design elements should be located in a separate folder in the DAM from the finished asset. For example, two headshots will be added to a final graphic. The headshots have a unique location in the DAM, and the final graphic has a unique location. Right now, it is a one size fits all strategy. Within a task, all content is saved to the same folder in the DAM. Can it be made possible to save content in the same task…
11 votes -
Lock Expiry Date Field in Pod Workflows Post-Review
We need to ensure expiry dates in Pod workflows remain accurate and compliant by preventing unauthorised edits after review. Currently, users can change the expiry date field even after it has been reviewed, which risks compliance issues and undermines governance efforts.
Please implement a lock on the expiry date field once a designated reviewer (e.g. Marketing Compliance) has completed their step in the workflow. This will:
- Prevent accidental or unauthorised changes
- Reduce manual monitoring
- Support consistent asset governance
If full lockdown isn’t feasible, a conditional lock or warning prompt would be a helpful interim solution.
14 votes -
Disable expiry date notifications for archived assets
Whether at the organisation level or the asset level, there should be a way to disable notifications for asset expiry dates when the asset has been expired.
10 votes -
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.
3 votes -
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.
3 votes -
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.
3 votes -
Duplicate Record Detection
Implement an automatic duplicate record detection feature that checks for existing records based on key fields before a new record is created. If a potential duplicate is found, PACE should alert the user and provide an option to review the existing record before proceeding
1 vote -
Inheriting parent permissions from default
While tagging newly created campaign to a parent the 'Inherit permission from parent campaign' box is automatically ticked. The less fluent user overlooks it and then is not able to manage their CPN access level - remove user or manage the view/comment/edit rights (Share). This 'Inherit permission from parent campaign' box should be unticked from default so the campaign creator has more flexibility in sharing it with users they need.
1 vote -
Not inheriting parent campaign permission's from default
While tagging parent campaign the new created campaign record inherits the permissions from default - the option is automatically ticked and for less proficient user may be easily overlooked. Then in the child CPN its owner cannot manage the user permissions (remove user or manage view/edit/comment rights). The 'Inherit permission from parent campaign' should not be ticked from default to let the owner (creator) decide on the permissions themselves.
1 vote -
Asset Owner from WRQ to TSK
When converting a WRQ into a TSK, the system believes the TSK creator uploaded the file and assigns that person as the asset owner, instead of the creator of the WRQ. This ownership carries through to the library, making notifications and reporting difficult. Please have the TSK inherit the WRQ uploader as the asset owner.
2 votes
- Don't see your idea?