05 August 2022

1. REST Services - ID Locator Improvements

The built-in ID locators can be configured regarding response codes, messages and format in case no objects were found.

This is particular useful in case the calling systems expects the error message in a certain format.

Also, you can evaluate conditions on the found object in order to allow generating more detailed error message in case certain conditions are not satisfied.

See example below:

<IdLocator type="tnr">
    <AllowWildcards>false</AllowWildcards>

    <Condition expression="current == Obsolete">
        <IfNotMatched contentType="application/json" statusCode="403">
            {
                "error": "E2322",
                "reason": "Bad status"
            }
        </IfNotMatched>
    </Condition>

    <IfNotFound statusCode="200" contentType="application/json">
        {
            "error_code": "E0003",
            "reason": "Object not found"
        }
    </IfNotFound>
</IdLocator>

For more information please see this document.

2. Fixed Bugs

Below is the list of fixed bugs as of this release.

Issue No Description

908

Allow override host name + port for the generated Admin API urls in case HTTPS is terminated by a proxy server / load balancer

906

End point used to test Payload configuration mentioned in the tutorials, was missing from the new Admin API.