Version 2023.08.2

What's new

Allow language specific attribute names and attribute descriptions

• Previously we would provide customers with the functionality to change the display names and descriptions of attributes that are used in the RITM UI. These name and descriptions would however be the same for each language. We now introduce language specific attribute display names and descriptions:
  • The defaults defined for the attributes via "Data > Attributes > Attributes list" are still used if not overwritten by specific ones.
  • Display names and descriptions can now be changed, for each supported and enabled language, by navigating to "Settings > Customisation > Translations", choosing "Edit translations" and using the new "Attributes names" tab on the dialog.
  • Note: Customers that already provided defaults too better suite their needs, might need to override the new defaults with more specific ones.

Allow language specific canonical names for attributes

• Customers can already use the existing functionality to use so-called canonical values for attributes to enable a drop-down for attributes in the RITM UI. An example would be the email address type of "Work", "Home" or "Other". We now introduce the ability to not only change the displayed name, but also the ability to do this per language:
  • The defaults defined for the attributes, as defined during setup or via configuration by Thales Professional Services, are still used if not overwritten by specific ones.
  • Canonical names can now be changed, for each supported and enabled language, by navigating to "Settings > Customisation > Translations", choosing "Edit translations" and using the new "Attributes values" tab on the dialog.

What's fixed

The /roles/assignable functional API would return a 400 error in some cases

• When the /roles/assignable functional API is called by a user with no admin role(s) we would return a 400 error in the response. The functional API has been improved to return a proper response, in this case with no assignable roles found.

The functional API to edit users doesn't take roles defined on the groups into account

• For customers that are using the multi-company feature and are managing users via the functional APIs, we don't always allow to manage roles that are configured on a group level. We introduced a new version of this functional APIs to allow the management of roles, regardless if a role is defined in an admin role or on a group level. Note: These new versions of the functional API /api/v2/user/:uid (PATCH) and /api/v2/user-update (POST) are more strict and some of the error responses changed slightly.