Ometa Framework Release v5.6.0

Version 5.6.0 of the Ometa Framework has been released with the following new features.

Breaking Changes

Due to recent changes in SharePoint’s behavior to enhance security by preventing custom scripts, we have made necessary adjustments in this feature release. As a result, we have removed support for the following Building Blocks, which required setting NoScriptSite or DenyAddAndCustomizePages to false:

  • SharePoint.BuildingBlocks.UserCustomActions - Delete User Custom Action
  • SharePoint.BuildingBlocks.UserCustomActions - Ensure User Custom Action

We apologize for any inconvenience caused by not adhering to semantic versioning in this instance. This change was essential to align with Microsoft’s updated policies.

For more details, please refer to the official Microsoft documentation.

Changed Behaviour

Obiz Suite: Modern Forms

The URL of the object manger to create modern forms has changed from [core service]/obiz-suite/bc/object-manager to [core service]/obiz-suite/nexus/object-manager.

URL Change

Performance Improvements

Transaction Logic to BCSP Queue

Transaction IDs for Efficient Processing: Previously, if a large batch of case creations was in progress, any subsequent single case creation requests had to wait for the batch to complete. With the introduction of transaction IDs, workers now process tasks from all transactions evenly, reducing wait times.

Simplified Case Creation: Previously, creating a simple case without actions generated three queue entries (creation, validation, and permission), requiring three queue workers. Now, only one queue entry is created, significantly reducing resource usage.

Enhanced Permission Queue Triggers: Database triggers for permission queue entries were generating excessive entries, causing unnecessary worker activation. These triggers have been optimized to prevent the creation of redundant permission queue entries, improving overall efficiency.