NoteThese notes catch up with several releases since our last published update on 2024.3.28 and are current as of the 2025.4.24 version of the platform.

Feature Enhancements

Improved Filters

• Tag Filter
  • Users will only see tag options corresponding to items currently visible in the list pages (Datastore, Container, and Field List).
  • The same filtering behavior has been applied to Anomalies and Checks within the datastore context.
  • If no visible items contain a specific tag, a No option found message will be displayed in the filter dropdown.

Scan Operation

• Scan flow
  • The scan form has been reorganized to improve the user experience.
  • Now, the following steps to configure the Scan Flow are Check Categories, Reading Settings and Scan Settings.

• Enrichment Settings
  • The Remediation Strategy option has been moved to Enrichment Datastore Settings.
    • The option will be a Datastore global value.
  • Also, the Anomaly Rollup Threshold and Source Record Limit can be configured as defaults.
    • During scan operations, these options will be pre-filled but can still be edited within the scan form.

Tree View

• The tree view layout is now adjustable, allowing users to customize it to their preferences.

• The footer in the tree view can be expanded or collapsed based on user needs.

General Fixes

• Filters
  • Fixed an issue where filters behaved inconsistently when navigating between different datastores.
• The container page is not loading
  • Fixed a bug that caused the container page to fail to load under certain conditions.
• General Fixes and Improvements.

API Changes

Incoming Breaking Changes

• REQUEST PAYLOAD: The fields enrich_only and enrichment_only will be replaced by enrich_container_prefix and enrichment_prefix and will affect the following endpoints:
  • POST /datastores
  • PUT /datastores/{id}

• RESPONSE PAYLOAD: The fields enrich_only and enrichment_only will be replaced by enrich_container_prefix and enrichment_prefix and will affect the following endpoints:
  • GET /anomalies/{id}
  • PUT /anomalies/{id}
  • POST /containers
  • GET /containers/{id}
  • PUT /containers/{id}
  • GET /containers/{id}/profile
  • GET /containers/{id}/scan
  • POST /containers/{id}/scan
  • PATCH /containers/{id}/favorite
  • GET /container-profiles/{id}
  • GET /container-scans/{id}
  • POST /datastores
  • PUT /datastores/{id}
  • GET /datastores/{id}
  • PATCH /datastores/{id}/favorite
  • PATCH /datastores/{datastore_id}/enrichment/{enrich_store_id}
  • GET /field-profiles/{id}
  • POST /operations/schedule
  • PUT /operations/schedule/{id}
  • GET /operations/schedule/{id}
  • GET /operations/{id}
  • POST /operations/run
  • PUT /operations/run/{id}
  • PUT /operations/rerun/{id}
  • PUT /operations/abort/{id}

• POST /operations/run, POST /operations/schedule, PUT /operations/schedule/{id}, POST /flows, and PUT /flows/{id}
  • DEPRECATE PARAMETER: remediation (To specify a remediation strategy going forward, use the new enrichment_remediation_strategy field available in the POST /datastores and PUT /datastores/{id} endpoints.)

As usual, our User Guide and accompanying Change Log captures more details about this release.