Skip to content

API Engine Release Notes - 1.1.2025051626.191680

API Engine 1.1.2025051626.191680

May 16, 2025

*The following updates were applied to:  API Engine Library 1.17.2025051426.190995

New Features and Functionality:

  • Primary Key Mapping Enhancement

    • Use Full Path in Source ID - The full path can now be used to specify which element is assigned to a primary key field.
    • Improved Mapping Flexibility - The mapping filter can be used in conjunction with the full path to streamline field mapping.
  • API Automation Enhancements
    • Group Step Activation Logic
      • When an automation group is enabled:
        • If none of the steps are active, all steps will be enabled by default.

        • If at least one step is active, a prompt will appear to confirm whether all steps should be enabled.

    • Ability to run a single task on a specific automation step.
    • When an automation group is enabled, all the steps will be enabled by default if none of the steps are active. If at least one of the automation steps in the group is enabled, then the user will be prompted to decide whether they want to enable all steps.
  • New Procedure in API Message
    • A new procedure, IsSuccess, has been added to the SENAPI Message table.
      This procedure calls the error processing method from the API Function’s interface implementation and exits with the inverse result of the IsUnsuccessfulAPIRequest procedure.
  • Performance Improvements
    • Faster Response Processing - Response processing logic has been significantly optimized, delivering performance up to 10x faster than the previous version.

    • Optimized Mapping Filter Logic - When a filter is applied, the engine now searches only the children of the specified parent element, improving performance.

Corrections:

  • Missing Permission Added

    • Read and insert permissions for the Retention Policy Setup table have been added to the SENAPIDataRetention codeunit.

  • GraphQL JSON Payload Generation Fix 

    • The escape character handling for JSON formatting for Graph QL payload is now correctly managed by the API Engine.