26th of September, 2023

Service

Organization Management

We have now implemented a new sign up and management experience for your Loome Organization. As an owner of a Loome Organization, you can manage your Loome tenants, user and API access, provide billing and technical contacts and view subscription details.

New users will also be redirected to this application when signing up to Loome, and can sign up for Loome Assist, Integrate, and Monitor in one location.

We will be providing further functionality via this app in future updates.

API Keys

API Keys have been enhanced in this release and standardized across Loome Assist, Integrate, and Monitor.

All keys now employ an expiry date. As part of the migration this will be set at 2 years for existing keys, but is configurable by you and will apply the next time a token is acquired for an API key.

You can also configure firewall rules to lock down what IP addresses an API Key can be used from.

API Keys now require you to assign permissions before they can be used. API Keys can be assigned an administrator role at the tenant level, or you can choose to assign an API key to a specific role in a specific project in order to limit its access. This is done via the existing user controls at the tenant and project level for user access. You will now be presented with the option to add users or add API Keys when assigning permissions.

As part of the migration, all existing API Keys will be added to the administrator role at the tenant level, and can then be modified by you as needed.

Additionally, new API Keys now require a separate client secret to operate, this adds a level of security when communicating API Keys to users. This will not affect existing API Keys, but you may chose to retire these existing API Keys and create new, more secure API Keys as needed.

API Keys can continue to be managed by tenant admins from within Loome Integrate, Monitor and Assist, or by organization admins via the new organization management app.

Improvements

  • Added tooltips to custom fields on the results view to improve readability of values.
  • Added a decimal custom field type.
  • Custom date fields no longer display with a static time component in the UI, or export to excel with a time component.
  • Improved UI for user management.

Fixes

  • Fixed an issue where a rule could not be edited if the last run by user no longer exists in the tenant.
  • Fixed a bug where creating a number column with NULL as a default value could result in duplicate records in the output table.
  • Fixed issue where date filter didn’t immediately filter upon date selection on results view.

Agent

This update requires agent version - 2023.09.24.1

Please download a new install script and update your agent to use new features, improvements, and fixes.

Improvements

  • Added a decimal custom field type.
  • Significant improvements to excel import/export speed and reliability.
  • Support for custom notes fields larger than 255 characters.
  • Custom date fields no longer display with a static time component in the UI, or export to excel with a time component.

Fixes

  • Fixed a bug where creating a number column with NULL as a default value could result in duplicate records in the output table.
  • Fixed an issue where an open data reader error may be reported on a rule that uses Azure Synapse.
  • Fixed an issue where an error relating to a column already having a default bound may be reported on a rule that uses Azure Synapse.
  • Fixed a bug where using a custom date field as a key in a manual record, duplicate records could be created when importing from excel.
  • Fixed an issue where you could not export a rule to excel when a custom list field has more than 256 items.
  • Fixed an issue where a rule name may not be updated in the LM__MAPPING table when changing the rule name.
  • Fixed an issue where user supplied datetime columns were incorrectly converted to local time in UI.
  • When a rule fails due to an agent issue, the agent will report the rule as failed when it starts up again, preventing rules from being left in a permanent running state.