Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Experience Analytics, Exchange, Watson Marketing Insights, Content, Web Content Manager and WebSphere Portal solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.
Connect with your peers and Acoustic experts on the Watson Marketing and Commerce Community
Submit ideas for other Acoustic Products:
• Watson Commerce
• Watson Supply Chain
One of the basic/core capabilities of a CMS is versioning of changes. Currently, this capability is not available and as a result, any accidental changes made by one author cannot be "undone". Persons who need to approve changes are unable to compare what they are being asked to approve to a previous version.
How will this idea be used?
User A is editing content and makes some drastic changes and publishes the item. The team later finds these changes were incorrect and need to put things back to how they were. User A (or another author with access) can go into WCH, and rollback to the previous version.
In another scenario, a manager needs to "approve" the changes User A has made. By leveraging versioning, he/she can compare the changes and decide is approval should be granted or denied.
|What is your industry?||Non-Industry Specific|
|What is the idea priority?||High|
|Link to original RFE|