You can now create an entirely manual data set or add manually entered rows to your source data using the Loome Monitor UI.
When manually adding rows to your source data, if you have created a row in the Loome Monitor UI but find that you already have a row for this record in your source data, you can easily merge the two rows together.
Any created data set will be available in your target connection if you would like to further integrate this data.
We now support Azure Synapse SQL in Loome Monitor. You can stage your data both to and from Azure Synapse SQL.
You can create a status and edit any existing record status after you have run a rule. This is based on the conditions you set and Loome will label a row with this status accordingly.
We have improved the process of editing a record so that each record is edited on a new page. In this new page view, you can also easily move from one row to the next to streamline your record editing process.
When multiple users are viewing the same results page, they will now be notified of any changes to records on that rule’s page. You will see the latest records on the results page and if another user updates a row at the same time you are viewing this page, you will receive a notification. This also means that you will be informed that a row is being saved and will not be able to edit another row until this is saved.
We’ve added the ability to create longer notes on the results view and increased the character limit on the notes custom field. If you have notes fields where you would like to use this higher character number, update your agent, re-run your rule and you will be able to use up to 4000 characters. You will need to manually modify the data type of existing notes fields.
We have improved our persistent staging processes to effectively stage your data, such as modifying key columns, and adding and removing columns.
To improve performance, we have moved metadata entities, i.e., custom fields, out of persistent staging. As well as improving performance, this will be more cost effective as it will not run persistent staging each time a record is updated. You can also add, remove, or change the name of metadata columns in your rule.
Renaming column names will depend on your selected connection as this may not be applicable in the target output, for example it is not supported for Azure Synapse SQL.
Communication rules will now be available after a rule is run once data is available in the results of a rule. Once you have run a rule, you can find communication rules on a rule’s edit page.
We have improved the user experience when a page is loading and provided more visual indicators.
We have added the option to access the results of a rule from its edit screen.
We have updated our slicers to use SlicerView instead of SlicerFunction.
We’ve updated the names of columns generated by Loome to be consistent with Loome branding. If you previously used columns such as DGStartDate, StartDate, and EndDate, they will now be called _LM_STARTDATE and _LMENDDATE.
We have updated the format of dates in Loome so that it is month, date, year, e.g., Sep 2, 2020.
We have fixed an issue where the number slicer for decimal columns was set at a stepping increment that was too high. We have increased the stepping for decimal columns.
We have fixed the incorrect names that displayed when creating a reference or glossary on the final button labels and query page.
We have fixed an issue where you could not select the ‘new record’ column from the column dropdown when creating a communication rule branch.
Fixed an issue where the reason a row was ignored did not display on the results page.
We fixed an issue where a number slicer would not load filtered results and caused an error notification.
We have fixed an issue where if a row was ignored while ‘Unresolved’ was the default status, it would not immediately update the results view and would still display the ignored row until the page was refreshed.
We have fixed the issue where a connection could not be changed when editing rules.
The name of a rule will now be displayed correctly in the execution slide-out when first running a rule.
This update requires agent version - 2021.03.17.1
Please update your agent to use the features and improvements above.