We've been continuing to update and modernize user experiences throughout OneDrive and SharePoint. And as we noted earlier this month, we’re making it easier than ever to share these updates with mo...
Updated Jan 24, 2019
Version 1.0
Blog Post
Thank you.... i do understand what you are saying. I work within a Quality department and control all company procedures and forms on our Qality Management system certified under ISO 9001. Effectively I have edit rights to all minor and major versions and the rest of the company can only read the majors.
We apply the require check out feature as protection that none of our documents would be updated or modified accidentally. On the document footers we record the major version number and the date modified of that major....ie If I want to publish a major revision on 17 July, I need to quickly edit the document itself to put the new version number and the date 17 July in the footer of the document. Then publish it on that date. Our SharePoint library is effecively our master document register that we can show an auditor and we need to ensure the version no and date on the document match up with the version number and modified date columns in the library.
Would appear our tenant received a SharePoint update last week with all the new features mentioned in this blog post. The simple point I'm making is that prior to the update, if I wanted to "publish" a document to major......when I select "Check in" the pop up window asked me if I wanted to override the current draft (minor) or go straight to major (this is what I selected), if i wanted to retain check out, and then comments for the what has changed... ie I was effectively checking in and publishing to major in the one action.
Now post the update, I have to check in the minor and then publish as 2 seperate actions. The problem is the check in button does not go green unless I add comments, which I don't need to record for the minor. Then when it's checked in, the publish option does not appear in the menu - I have to refresh the page to see it. Then publish, add comments etc and it's done. It's just a more long winded process now.
I know this askes the question, why do we need minors? This is because we have custom columns in our library containing properties about the document, e.g. ref number, division, category, doc type etc and sometimes these may need to change but the document itself hasn't changed so to keep our version records accurate we will make chnages to those columns and check the document in to a minor to save those chnages and then will only publish the document to major when there has been an actual change to the document itself.
Just seems such a shame that to incorporate the check in / out of multiple items, the window which previously popped up for a single item now longer does.