Release 2024.9 introduces REST error handling

This release enhances REST error handling, making it easier for app users to understand the cause of errors.

Mobile Apps & Builder

New features & improvements

  • REST error handling - Errors returned by REST endpoints are often too technical for end-users to understand. Jigx allows you to customize these error messages, enhancing user experience by making the messages clearer and ensuring users know the error is not their fault. Additionally, you can configure how to handle items in an error state, such as retrying the operation or deleting the item. For code examples see REST errors.

  • Additional information on error handling for datasources has been added. Global datasources, which previously failed silently, now display an error screen when issues occur. Local datasources also trigger an error screen when errors are encountered, with detailed error logs providing additional context. The following errors are detected, with details displayed on the error screen:

    • Non-existent datasource error: This occurs when a datasource cannot be found, often due to an outdated name, a typo in an expression, or a missing table in the default file.

    • Query processing error: This occurs during the execution of a datasource query, such as when an SQLite query contains syntax or logic errors.

  • Added the ability to use solution settings expressions to build default values for parameter values in function files, for example: value: =@ctx.solution.settings.custom.restStorageApiKey

Deprecated

  • The errorTransform property in REST functions has been deprecated. If you currently have errorTransform configured in your function, the solution will continue to function as expected to support backward compatibility.

Jigx recommends you update the function file to use the new REST error handling properties that provide greater control over errors returned from the REST service.

Known issues

  • Issue: When using a SELECT statement in a datasource query that does not return an id in the result set, and the dataset is large, it can negatively affect the solution’s performance. This is especially noticeable when the data is used in a dropdown.
    Workaround: Ensure that the query always returns a unique id in the dataset. The id must be lowercase.

To see the full list of new features, bug fixes, and improvements in Jigx 2024.9 see the release notes .