You are reading the documentation for an outdated Corteza release. 2024.9 is the latest stable Corteza release.

2022.9.9

Released on: 2023.04.05

  • Added pagination on inline record lists when in view mode. The change was added to have consistency and better user experience when using inline record editing (e0ae508).

  • Changed record import modal to allow users to map values to record and user fields. The change was made to allow users to map values to record and user fields when importing records. The change was made by removing the code that was preventing the users from mapping values to record and user fields (0cf81dc).

  • Changed workflow triggers to not automatically add constraints after an event type is selected. The change was made to prevent users from getting a console error when fetching workflow triggers without provided constraints (7a9802a).

  • Fixed Cannot read properties of undefined error when trying to fetch workflow triggers without providing constraints. The fix was made by adding a check to determine if a constant has a name Also, the automatic addition of constraints after an event type was selected is now removed (7a9802a).

  • Fixed missing support for the STD aggregation function on MySQL databases. The STD function was present in past versions. The fix was made by adding an expression handler for the function and only allowing it for MySQL databases (3ec7d19).

  • Fixed record lists raising Could not load record list: can not change module on a record when interacting with an imported namespace. The issue was caused because the import logic didn’t define any model constraints. The fix was made by making the import logic apply model constraints when defining the model, as well as defining the record revisions model (a554e28).

  • Fixed future/past values not being selectable if DateTime field has future/past only values option applied. The fix was made by disabling the future/past only option on record list filter (24a3197, ffbaba2).

  • Fixed Admin user view not showing any data when 'Confirm email address' was clicked. The fix was made by refetching the user again on Admin when the user is confirming the email address (e76fb09).

  • Fixed field kind not being updated in modules after being selected. The fix was made by updating the module field kind after it is selected (1018, 1018).

  • Fixed users not being able to update their records due to the “Could not update record: failed to complete transaction: Error 1366: Incorrect decimal value: updated for column operation at row 1” error. The fix was made by changing the datatype and also by doing a rearrange of the columns of the record revisions table for consistency (b585dfb).