Improve version control mechanism to consider also PI AF Analysis & Notifications Elements

Improve version control mechanism to consider also PI AF Analysis & Notifications Elements: Background: When adding or removing an attribute to an Element in PI AF, the element's revision number is incremented (as expected) which makes the revision history to be correctly represented to the end user with a clear picture of the changes performed. Currently PI Analysis & PI Notifications are not version controlled (at least not from an end-user perspective). Changes performed via PI System Explorer are audited but there is no version\revision number exposed to the end user to enable a clear view of history of changes performed. Also, using the PI AF Audit Trail to search for (and understand) a change done in PI Analysis can be quite a tedious task and requires extensive experience in PI AF. Enhancement Request: Whenever the user edits (add new, update or delete) an existing Analysis, the revision number of the AF element to which the Analysis is linked should be incremented and then the revision history will be correctly represented to the user. *comment: Since PI Analysis is an independent element, it is worth while considering to add a version\revision history section in the Management tab in PI System explorer, so when a user selects an analysis, they will be able to see the revision history of that individual element.