Resolving anomalies: Overview

Review and resolve the anomalies that Guard detects.

About resolving issues

If multiple anomalies are detected when Guard scans your instance, you should analyze the issue to see if you can find a solution that prevents the issue from recurring. 

You can resolve an anomaly manually, such as one-off anomalies like individual data entry errors like a typo. However, when recurring anomalies are detected that affect multiple records, such as missing serial numbers or asset types, then further investigation is required to resolve the anomalies.

When you review anomalies, you are provided with the cause of the anomaly and an action. You can use this information as a starting point for resolving anomalies.

Missing data anomalies

Let's say multiple records don't contain a value for a field - missing data. Click the record. On the left  sidebar, the data source for the record is displayed. (In most cases, unless the record was added manually or imported, the source of the data is an integration.) 

Click Configuration and open the Integrations: Block view page, and then click the Assets integration. On the Integration details page, open the Mapping section in edit mode. If the field is mapped to Oomnitza, click Sync Sessions and review the logs to find out why the field value is not being populated. 

If the data source for records is a spreadsheet, review the spreadsheet and ensure the field and its value is added to the spreadsheet.      

Let's say the missing data can't be retrieved when Oomnitza syncs with the data source. For example, you added a custom field to enrich the data that is collected about assets. In such cases, you can create a workflow to populate the field's value. When Oomnitza syncs with the vendor application, the workflow is triggered and you get your missing data.

Creating workflows: Overview  Importing records

Naming anomalies

You might have multiple integrations as data sources for your records. One data source calls the manufacturer, Dell, another Dell Inc., and so on. You really don't want to resolve this issue manually! So, what can you do? Create a normalization rule so you get the same name for the same thing. This will resolve naming issues and ensure that you use the same name for the same thing. 

Data normalization: Overview