I note with some alarm that the Annotations module is being disabled from 10.4.0 onwards. Within our DataMiner systems, we have made quite extensive use of this. It allowed us to use "generic" visual files as templates for services, but to have service/site specific information readily available to the operators when viewing the service in Cube.
So, the question is if this is being removed, what is the practical alternative to replace it? The initial potential options available in DataMiner that come to mind seem to be: Notes, Documents or Properties. However, none of these really match our current use of Annotations.
Notes: While conceptually the “closest” match to Annotations in how they are associated with a service, the intended role of Notes is different. They are more the yellow “post-it” functionality for temporary issues around a service to be shared with everyone, rather than permanent specific information. Yes I know they can be set not to expire, but it is still too easy to delete them with a single click and they only allow you to add plain text to them, rather than the richer HTML structured information (e.g. lists, bold text, embedded pictures) that is available with Annotations.
Documents: While these allow you to theoretically add any type of document to the system, they are not service specific. They are either general documents that are available whichever service you are looking at, or they are associated with an element that is included in the service, either related to the protocol/connector for that element type and therefore not specific to the service or related to a specific element instance. There is no way of associating a document which could contain information about multiple elements in the service with a specific service. In addition, any document needs to be viewed in a separate application. The contents are not shown directly within Cube as Annotations are.
Properties: One could theoretically create a custom “Annotations” property and potentially display the contents of it on a separate page in the visual file. However again you are limited to simple textual information, and I suspect that there is a limit of the size of the contents of a property.
I wonder what the reason for removing the Annotations functionality is. Is there a technical reason, or was it felt to not be widely used? Personally, we found it very useful and its removal is arguably a loss of key functionality and a retrograde step in the usability of the DataMiner system for our operators.
Does anyone else feel the same? Or are there other alternatives that people are using to provide the equivalent functionality?
Hi Paul,
First of all, thank you so much for sharing your case with that level of detail. I would like to find an acceptable way forward for you. Ok if I send you a meeting invite to go in full depth on your case?
The main reason for retiring Annotations is general usage indeed compared to alternative features in DataMiner.
Just for transparency towards the broader community. Current idea is to leverage dashboards for the service specific data.
This means still one Visio that is shared for all the services. Each service that has extra service specific information holds that information in a specific dashboard (instead of in an annotation). That dashboard is displayed embedded in a dedicated Visio page (via placeholders that link to either service name or id). With this, we end up with an extra Visio page on the card instead of the Annotations page on the card, but the content would be the same.
Hi Pieter, yes happy to have a call to discuss possible ways forward.