Skip to content
Request Demo

API Engine Release Notes - 1.20.2026012227.245414

Picture of Suite Engine Support

API Engine 1.20.2026012227.245414

January 23, 2026


Features

  • StringTemplate Value Processing Function

    A new Value Processing Type enables dynamic text construction using placeholder syntax and extensible pipe functions.

    • Construct dynamic strings using {{variableName}} placeholder syntax 
    • Apply transformations via pipe functions: {{var|EnumName:FunctionName}} or {{var|Enum:Func("param")}}
    • Built-in functions include Uppercase, Lowercase, UrlEncode, UrlDecode, EscapeDoubleQuotes, BooleanToIntegerText, and ZeroToBlank
    • Supports multiple placeholders, nested resolution, and value caching within a single template
    • Includes circular reference protection to prevent infinite loops
    • Extensible architecture allows any Value Processing Type to work as a pipe function

  • Data-Driven Trigger Settings for API Mapping

    New configuration options on API Mapping provide granular control over field validation and trigger execution during response processing.

    • New Boolean fields: Validate Field (default: true), Run Insert Trigger (default: false), Run Modify Trigger (default: false)
    • New API Mapping Card page (ID 70338625) for detailed mapping configuration
    • Validate Field option enabled only when Field No. is populated
    • Run Insert Trigger enabled only for RecordNode type mappings
    • Run Modify Trigger enabled for TableNode and RecordNode type mappings
    • Backward compatible: existing mappings retain current behavior with no changes required

  • ProcessAPICredential Password Parameter Overload

    An overloaded ProcessAPICredential procedure now accepts a Password parameter, providing flexibility for credential processing scenarios that require explicit password handling.


 

Corrections

  • x-www-form-urlencoded Payload Now Respects Do_Not_Include Setting

    Fixed an issue where variables configured with "Var Value Null Behavior = Do_Not_Include" were incorrectly included in x-www-form-urlencoded payloads as empty values (e.g., fieldname=). Empty variables with Do_Not_Include are now properly excluded from the payload.