This place is where you can suggest, discuss, and vote on ideas. If you want to create an idea for an other related product choose the appropriate group on this page.

When you select to create a new idea, there are a few things you can do to ensure RWS Development and other community participants understand the idea. See here for Idea best practices.

  • Publish from Favourites view

    Will Wallace
    • Under Community Review on
    • 0 Comments
    It would be useful to be able to publish items in my Favourites - either from the Shortcuts window or the Favourites list view. I have a number of items which I republish regularly, which are spread out among different publications. Currently I have...

  • Add Download attribute option to Insert Hyperlink

    Steve Redgewell
    • Under Community Review on
    • 3 Comments
    In the CME, when editing a rich text field, it would be useful to have a Download attribute, to convert any Hyperlink (inc Component links) to a Download. https://www.w3schools.com/howto/howto_html_download_link.asp If this field is used in the CME...

  • Extend GraphQL API with better support for categories and keywords

    Mattias Ekwall
    • Under Community Review on
    • 0 Comments
    We are in the process of upgrading our Tridion installation, and in this process we've worked on rewriting various parts of our codebase that is written in C#. We are in the need of some help when it comes to some parts related to your GraphQL API and...

  • Content Editors should be able to initiate translation workflow and upon completion, transition into publish bundle workflow automatically.

    Cyril Tano
    • Under Community Review on
    • 2 Comments
    Currently, the translation workflow process is initiated and completed separately from publish workflow. Once translation workflow is complete, the individual items/components become major versions, and editors then need to go in and initiate the publish...

  • Order the order of shown Component Templates

    Vanessa Rijkens
    • Idea Delivered Partially on
    • 4 Comments
    In Classic the component templates are shown in alphabetical order, when adding a component with multiple CT's to a page, not optimal, but understandable. In ES however, the order is based on creation date or ID, which results in a random looking order...

  • Impersonate user or user group to check rights on publications, structure groups and folders

    Erwin Broersen
    • Duplicate on
    • 3 Comments
    Setting access rights in Tridion is quite a challenge. In our case we connect with SSO and rights are set based on our profile. The team is always administrator with all the rights. This means we always need to ask a user with certain rights to help out...

  • Possibility to create more visual overview in schema's

    Vanessa Rijkens
    • Under Community Review on
    • 0 Comments
    As a schema designer, I would like to be able to create more overview in schema's. For example by adding sections, lines, colors, subtitles etc. This to create for example a section for desktop content and a section for mobile content. Or to be able...

  • Sort Publication Lists by title and not ID.

    Mark Saunders
    • Under Community Review on
    • 0 Comments
    In the 9.5 UI publishing view we have the option to select/deselect specific child publications from the publish transaction. However, the list is sorted by TCM ID and apepars cluttered with it not being in alphabetical order (as other Publication...

  • Where Used report not exportable.

    cmssupport11 DCT
    • Under Community Review on
    • 2 Comments
    If we want to get impacted pages for components, we could use Where Used report but this pop up report is not exportable right now. Custom OOTB implementation to achieve this will be helpful so that we are either able to copy the data or export it.

  • Make the 'Publishable check' less sensitive

    Vanessa Rijkens
    • Accepted, Not Yet Planned on
    • 1 Comment
    In Experience Space we now have editors unchecking the 'Publishable check' on folders or structure groups without noticing. Resulting in changes not reflecting on site without any hints whatsoever. For us a nice new puzzle :-) but for editors missing...