- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We are in the process of transition our IT "documentation" from its current location into ServiceNow. A large majority of it is going into the Knowledge Base which is perfect for How-Tos however there are some items that we are not sure what to do with.
Information Technology/Data Center items such as:
1) ISO files (for instance VeeamRecoveryMedia.iso)
2) License files (.lic files)
3) Purchase and Renewal information
4) Various reports: Preventative Maintenance, Device Health Check
What module(s)/location(s) in ServiceNow would work well for the type of information listed above?
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
That's an interesting architectural decision. I definitely wouldn't recommend moving large amounts of unstructured data / blob data into SN.
ServiceNow environment come with a storage limit and a pricey licensing model for overage. It's also not performative as SN doesn't store files as blobs. It chops them up and stores them in tables. The reason large files take a while to download in SN is because it has to stitch those records back together and then pass it on to the user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
1 and 2 would work best in a document management system such as SharePoint.
3 sounds like a fit for contract management
4 depends what information these contain, and what attributes you require in order to report / drive workflows from.
ServiceNow can hold attachments, but it shouldn't be seen as the go-to for all files 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you for the response, Kieran!
We actually have all of the information currently in SharePoint. Our company is hoping to move everything out of Sharepoint to ServiceNow.
So, by the sounds of it, ServiceNow may not have the type of "repository" we need for the items I listed in my original post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
That's an interesting architectural decision. I definitely wouldn't recommend moving large amounts of unstructured data / blob data into SN.
ServiceNow environment come with a storage limit and a pricey licensing model for overage. It's also not performative as SN doesn't store files as blobs. It chops them up and stores them in tables. The reason large files take a while to download in SN is because it has to stitch those records back together and then pass it on to the user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you for sharing your knowledge and experience with SericeNow. That is most helpful for me in learning the ServiceNow platform. The information you provided definitely makes sense and is a good recommendation.