Unpublished changes indicator

[#1]

Request for Feature Enhancement (RFE) Summary:	A quick indicator that a page has unpublished changes (e.g., something like a blue dot that indicates an unread message)
Use-case:	Large websites that get change requests from different avenues. Sometimes they overlap, creating issues when other changes get published before they should.
Current/Experienced Behavior:	An author must do a good deal of sleuthing through version history to find out if there might be unpublished changes to a page. That information can still be incomplete at times, depending on the workflows the previous author executed.
Improved/Expected Behavior:	An author would see this easy indicator on the Site Admin screen, so they could know immediately if there are unpublished changes. It will also serve as a reminder to publish the changes if they should be published.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM 6.4
Customer-name/Organization name:	U.S. Bancorp
Screenshot (if applicable):
Code package (if applicable):

[#2]

This is such a great idea. Our bank has 150 product teams and some of their pages, products, and disclosure statements overlap. This means on occasion we have more than one product team requesting different authors to update the same page. Having an indicator light like this will help us know right away if we should be mindful other authors having unpublished work on a page.

[#3]

A great enhancement idea! This would be great for large enterprises like mine with many authors and teams, preventing mistakes and easing the anxiety that comes with publishing content!

[#4]

Love this idea as well, for all of the reasons mentioned in the last two comments.

This feature -- which existed in AEM Classic UI --- is one of the reasons many authors across our organization still prefer that interface over Touch. 

I would go a step further and ask if there is any way to provide more context into the modification itself, surfacing a message somewhere in the UI.

A modification can be triggered by a component being opened and edited and saved. It can also be triggered by a component being opened and saved - without any edits taking place. We have plenty of comms across our authoring teams: "Don't mind my modifications - I was just poking around" ... and "Are there any pending modifications? If yes, I need to back them out so I can go publish."

^^^ Particularly important for us in highly regulatory environments where we are concerned with materiality, which can be the change of just a single word of number. 

[#5]

Echoing all the above, this would be incredibly useful!

[#6]

Totally a great idea. Can help solve a lot of overlapping edit issues. 

[#7]

Good to have this feature.

[#8]

For aem 6.5.12 you guys can use this package.
https://github.com/pedapudibhargav/publishStatusIndicator6.5.12

For other versions please checkout the JSP file /apps/cq/gui/components/coral/admin/page/columnitem/columnitem.jsp available in the package.

[#9]

Same solution for 6.5.4 version,  

https://github.com/pedapudibhargav/publishStatusIndicator6.5.12/blob/main/Publish_Status_Indicator_6...

Thanks,

Venkat.M