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.

  • Non-localizable fields

    Ron Grisnich
    • Under Community Review on
    • 4 Comments
    Fields marked as non-localizable in a schema cannot be edited in localized components (should appear as read-only field in local copies). Example of configuring a non-localizable field:

  • Log more actions of users

    Vanessa Rijkens
    • Under Community Review on
    • 2 Comments
    As a lifecycle manager, site-admin or other senior user, I want to be able to see more logs on what users do. What users are (in)active, who deleted a structure group or page, who renamed a folder, what was a previous publish date for a page. Etc. etc...

  • Recover Deleted Items

    Paul Brou
    • Accepted, Not Yet Planned on
    • 4 Comments
    Actually, the question would be " How to Restore Deleted Items? " There are several creative ways to do it but would a concept of "Recycle Bin" within the CME be helpful? With that, Users could recover intentionally and inadvertently deleted items with...

  • Rename XPM Page Types and Content Types into Prototypes

    Luca Agostinelli
    • Accepted, Not Yet Planned on
    • 1 Comment
    The concept of Page Types from a Content Modeling perspective is often confused with the Experience Manager Page Types. Clients often believe that XPM requires creation of as many Page Prototypes as the Page Types identified in the Content modeling...

  • Introduce versioning for the item types that are not currently versioned

    Dominic Cronin
    • Duplicate on
    • 3 Comments
    Structure groups and folders definitely need to have versioning. It's too easy to change something and then be unable to undo the change. The same applies to publications (especially given the amount of care needed with Content porter to avoid clobbering...

  • Translation Manager - Allow aggregation across schemas

    Jacques Kors
    • Planned for Future Release on
    • 2 Comments
    Currently, when using aggregation for multiple schemas, the aggregation is split across schemas. this means only components of one schema are combined into one aggregated file. a job with components based on X schemas will still result in X files. ...

  • Retain content in page metadata when changing page templates

    Cyril Tano
    • Under Community Review on
    • 1 Comment
    When creating a new or editing an existing page, the system should allow the author to change page templates while keeping any text currently entered into common metadata fields. Currently, if an author fills out metadata fields and realizes the wrong...

  • Display Publish Date next to version number in version history

    Arijit Chowdhury
    • Under Community Review on
    • 4 Comments
    This enhancement request is from a Financial Services client in North America. -- "To provide evidence related to record-keeping needs, the Compliance department would like to know when specific versions of a piece of content actually were published...

  • "Collapse all" button in Publications panel

    Ron Grisnich
    • Under Community Review on
    • 3 Comments
    Button to collapse all publications in the Publications panel.

  • Please do not automatically populate the "Title" field of a component link with the name of the component

    Amy Pearson
    • Under Community Review on
    • 0 Comments
    Currently when linking to a component within Tridion, the title field is automatically populated with the name of the component. We have to delete this out because a) the title attribute is really for a tooltip which is rarely used and decreases usability...