XavaPro 7.7 released

XavaPro 7.7 has the next new features:

• AI chat can be disabled for a role.
• AI chat cannot access data from modules not available to the user's role.
• Members excluded for a role are not accessible from the chat for users with that role.
• Read-only members for a role are accessible from the chat but cannot be modified via chat.
• Multitenancy supported in AI chat, chat can only access data from the current organization.
• Deleting an organization now requires typing a confirmation word in a dialog.
• Works with OpenXava 7.7.

AI chat by role

The flagship feature of OpenXava 7.7 is the new AI chat, which by default is always available in the application. In OpenXava there is a way to completely disable it using a property in xava.properties. However, with XavaPro it is much better because we can disable the chat selectively by role.

Now in the roles module, we have a new field, AI chat:

For example, if in this case we unchecked AI chat, the chat would no longer be available for users with the "supervisor" role. This not only allows us to disable the chat selectively, but also to do it at runtime, without modifying or restarting the application.

AI chat security control via XavaPro

We have adapted XavaPro so you can use the security administration tools to restrict what can be accessed and what can be done from the chat. For example, if a role does not have access to the invoices module, when users with that role ask about invoices, the chat will not provide them with any data.

Even the granular security at module and role level is respected. For example, if in the products module for a certain role we specify that it cannot access the ISBN field and that the price field is read-only, like this:

If we ask for the ISBN of a product, it will not give it to us because it is an excluded field. In the case of price, since it is marked as read-only, it will inform us about it, but if we ask it to modify it, it will refuse:

In addition, we have adapted the multitenancy mechanism so that the chat respects it. Only the data of the company in which the user is currently logged in can be accessed.

Stronger confirmation for deleting an organization

Deleting an organization is an irreversible action and involves not only removing it from the list of available organizations, but also deleting all its data, its tables, and even dropping the database schema. This is something serious, and until now it only required a simple confirmation, like the one used to delete a record.

We have improved the process for deleting an organization so it cannot happen accidentally. Now, when attempting to delete an organization, a dialog like this appears:

First, it includes a detailed explanation of the consequences. Then it is necessary to type the word DELETE in the field, which prevents accidental deletion. Finally, the label of the button that performs the deletion is quite explicit.

Try it yourself

Demo: https://www.openxava.org/xavaprotest (User: demo, Password: demo)

If you want to try the admin features reply to this email asking for the admin password.
If you want to try the mobile features access to above URL using your mobile phone.

To learn more go to the XavaPro page.

If you're an Enterprise customer you will receive an email with the upgraded Enterprise edition.