Allow users to attach documents (jpg/pdf/xls/csv/xml/doc/vsd/docx) as CI's or CI attributes

Allow users to attach documents (jpg/pdf/xls/csv/xml/doc/vsd/docx) as CI's or CI attributes

We would like the capability of creating document CI types or to attach documents as an attribute of a CI.

Some examples of how we would use it would be:

Create an "Architecture" CI Type and attach a Vizio drawing, or have an architecture attribute for a business application CI which would allow you to upload a Vizio VSD, PDF, or JPG.  Clicking on the filename should then either view or download the uploaded file.

Create an "Workflow" CI Type and attach a VSD, PDF, or JPG drawing of the business process workflow, or have an attribute for a business process CI which would allow you to upload a VSD, PDF, or JPG drawing.

Create a "Business Continuity" CI Type and attach a docx or PDF business continuity plan, or have an attribute for a business process or Business Service CI which would allow you to upload a copy of the continuity plan.

There are many uses for the ability to attach and relate documents to CI's... seems logical to implement the functionality.  Currently there exists an configuration_document CI Type and an attachment_content attribute of CIT Attachment but they only allow for 'byte' type.  CMDB needs a way to upload content and display/consume/download content.

Dmitry P Super Contributor.
Super Contributor.
Hello, you could create a new one attribute "Link to file/specification", I use links to Confluence pages for such needs.
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

We've reviewed this request.  There is already a solution to allow "blob" data to be stored on a "ConfiguirationDocument" CI Type.  However, the methods to do this are difficult to accomplish and there is no GUI to allow this.

So, I'm going to accept this ER from the perspective of providing a method to create a UI to populate the "blob" attribute  with attachments.

Keep in mind this is a VERY dangerous thing to do.  Attaching documents and files to a CI could easily cause OOM situations on the probe and memory situations in the database - even files as small as 8M. CMDBs are not designed to act as document retrieval systems, even though they can be used this way.  If we implemented this capability, we owuld also implement a method to limit the size to "protect" the user from causing poor or down performance on the UCMDB or probe infrastructure.

mike_toronto2 Honored Contributor.
Honored Contributor.

@DmitryP We used to use links as well but found that people were often not updating them when moving or renaming a document.  People would follow the link and NOT find whatever document they were expecting and thus, we get into the game of "Is CMDB data correct?".

@Bill_Dyck Although the CMDB isnt a document retrieval system, other CMDB vendor offerings do offer plugins to create and manage electronic documents within your instance.  The respective plugin adds a layer of control around any document by providing workflow, storage, security, and categorization options. It can be used for a variety of internal documents, such as policies and procedures, compliance documentation, and knowledge articles. Because it is integrated within the CMDB instance, it offers a seamless alternative to 3rd-party systems.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.