Idea ID 1680119
In DDMI, we had access to run direct database queries to pull out the OSInstalledApps data which originated from the scan file. We would run reports for OSInstalledAppDescription like %visio% so we could match any with an OSInstalledApp for Visio 2016 Pro to the enriched data to ensure that what was really installed as Pro reports as Pro.
Historically, with each release, we have always found issues where the edition is flip flopped during the teaching/enrichment process from the master SAIs. How does Micro Focus suggest customers validate their data if we can’t run direct database queries and we do not want to have to open 30,000 scan files each time an application is patched to ensure the enrichment is happening correctly?
We are now using UDi and we already had to open multiple tickets to Micro Focus Support because we stumbled upon (for example) Visio Pro and Std being flip flopped. We need to be able to proactively find these. Therefore we would like to make sure some form of enhancement is entered because we have to be able to validate the data. Otherwise, our customers are going to stop trusting our data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.