How it works
How can I capture actions?

Loome enables you to create a rule for your dataset by connecting directly to a source, and you can choose whether this rule should consist of only records from a source, a manual dataset you have added directly in Loome, or a combination of both source data extracts and manual input. Being able to add manual records to your dataset provides the additional flexibility that may not be available in read-only operational reports. Loome allows you to add custom fields that will provide the ability to capture more information in your dataset, such as the actions taken on data exceptions, by allowing you to add editable columns into your dataset which will then be included in tables in your target database.

How do I use those custom fields to track actions?

Once Loome detects an issue, you have the ability to add further context to the record using custom fields. This helps you easily overcome the typical issues of a read-only report and track the status of your records while capturing further information. By capturing additional data with custom fields, the reason why an issue occurred can be easily explained and tracked in the same data record, unlike read-only reports where this information would be stored in a separate report, if captured at all. This means you can analyze the effectiveness of your actions over time in a single report whilst improve your data quality.

A gif showing how to capture and track actions in Loome Monitor.