Improve dissemination of updated documentation and implement document versioning
We're not notified when documentation is changed by Accruent and this is frustrating when the changes are significant. For example, the Meridian 2019 R2 documentation said the Enterprise Server configuration database could be created with the 'dbcreator' role in SQL Server, however the documentation was updated at some point to state the the 'sysadmin' role is required.
Also, please add version history to all the documentation so we can easily see if we're using an old version compared to what's online.
-
Aaron Swain
- Jan 18 2020
- Shipped
Related ideas
Your comments have been discussed with the documentation office and will be implemented going forward. Going forward you can refer to this TechComm # MPS-35883
Attachments Open full size
Hi Rudi,
I appreciate your feedback.
I've been told several times that documentation is not updated but that's simply not true. Last year I had quite a few support cases that led to the online documentation being updated, and I've had two cases this year already.
Given that we all know documentation is updated silently, I think it's perfectly reasonable that we're given some kind of notification when online documentation is updated so we can perform our jobs with the current knowledge.
What's very common from other companies is to maintain an errata page in their KB. An errata page doesn't have to be detailed, it could simply list the sections that have been updated and on what date.
Regarding the version history, I'm referring to something as simple as version number on the second page or on the last page of the document. Again, it's really common for other companies to include a "document history" table or version number at the start of the document. Since we're dealing with a document management product suite, I'm honestly surprised there's no obvious version number on the documentation...?
Attachments Open full size
Hi Aaron, we normally do not update documentation of previous releases, but in this case we had to make an exception as we found out the published documentation was incorrect. By policy the online documentation is leading. Unfortunately our platform for online documentation does not have adequate versioning functionality. We are looking for ways to indicate changes like these better.
Attachments Open full size
I'll figure out what happened here, thx for the heads-up.
Attachments Open full size