We are going to release Docs/Rich Edit text editing history soon, it will work like this: [2021-06-29 16.16.01] Will you miss anything in this implementation? What are your cases for Docs/Rich Edit text editing history?

This is implemented and released (with changes highlights). Thank you for the feedback! [image] CHANGELOG: July 30 / Documents and Rich-text History, HubSpot integration Changelog Documents and Rich-Text History Starting this week, rich-text Fields and Docume…

Selecting a past version and having a toggle to highlight the changes vs today’s version (added lines colored in green, changed in orange, deleted lines in red) would be nice, Google docs style. Not a deal-breaker for me, but I see two main use case for this 1 recover a previous version in case so…

Yes – the ability to see differences between any version and the previous version, and any version and the current version would be super useful, to figure out which version you want to restore after a bunch of changes have been made.

How will this functionality integrate with the existing entity activity history? It looks like they are two separate history logs…

So far they are fully separated. We’d like to collect cases when you need the merged history. It’s possible to do, but we are not sure it is important enough.

100% agree with @Simon_JB and @Matt_Blais that a “highlight changes” will be important for this feature, at least long-term. Initial release can be without that, but to really be a good implementation it should have version differencing, ideally between arbitrary versions, but at least between immed…

[image] mdubakov: we are not sure it is important enough No it’s not that important, I just wanted to check I’d understood the implementation. [image] Oshyan: Two other things I’d love to have, that sort of work together. One is Named Versions , To be honest, I’d like support for name…

[image] Oshyan: Named Versions DEFINITELY THIS :sparkling_heart: I find named versions indispensable in Google Docs. We use Google Docs to author web page content, and I make a version name for a doc whenever I upload its contents to the web page (“Uploaded to website [date] - Matt”). That …

[image] mdubakov: So far they are fully separated. We’d like to collect cases when you need the merged history. It’s possible to do, but we are not sure it is important enough. What was your assumption for what a merged history would look like? I would think that you at least want something …

[image] rothnic: Otherwise, it would likely be confusing to people that the entity change history doesn’t include all changes. Yeah, that’s basically what I was getting at. But as long as people know to look in both places it’s not the end of the world, I suppose.

Adding my voice to the thread: highlighting differences since last visit would be great, or at the very minimum indicating that the content has changed (maybe with a visual denotation of changes in the clock icon?). The use case being: I’ve looked at that document a while back, has there been any c…

Document Changes History

Ideas & Features

mdubakov July 30, 2021, 2:51pm 13

This is implemented and released (with changes highlights). Thank you for the feedback!

1 Like

Topic		Replies	Views
Named Versions in Docs and Rich-Text Field History Ideas & Features history	0	446	July 30, 2021
CHANGELOG: July 30 / Documents and Rich-text History, HubSpot integration Changelog	5	1480	January 11, 2022
"Version history" of an entity Ideas & Features	0	44	August 22, 2025
Collabs on docs (specs, marketing plans, etc.) - how do you handle change management? Get Help	7	823	July 30, 2021
Versioning in Rich Text Fields (and entities as a whole, too) Ideas & Features history	22	2796	July 31, 2021

Document Changes History

Related topics