OpenXava 4.2.2 released

OpenXava 5.6 released

November 2, 2016

In OpenXava 5.6 the list remembers filters and ordering done by user to be re-executed choosing from a combo, you can rename the filter/ordering configurations produced. With this you no longer need 'My reports' action, so we have removed it. Also this v5.6 includes the new stereotypes DISCUSSION and SIMPLE_HTML_TEXT, partial select in baseCondition of @Tab, and many more things.

List remembers filters and ordering

When the user does any filtering or ordering a new entry is added to a combo on top of the list: Note that you can change the name of the filtering. Moreover, the columns configuration (that is if you add, remove or change the order of the columns) is remembered too. That is you can give a name to a filtering, ordering and column configuration, to restore it just with two clicks. These list configurations are stored by user. Don't resign yourself with the above screenshot, try yourself this feature with the live demo.

'My reports' removed

My reports action si no longer available by default: We have removed it because now practically all the features of My reports are available directly in the list, so we removed it as duplicated. Anyways, if your users do not like the direct manipulation paradigm but rather they still prefer to use cumbersome dialogs and wizards you can return to life My reports using the TypicalExtendedPrint controller instead of Typical, for example:

DISCUSSION and SIMPLE_HTML_TEXT

Recently we have moved from color to monochrome. We did it for most of the user interface, but HTML_TEXT still was using colorful icons. To solve it we have upgraded to the latest CKEditor version and adapted it to be consistent with the rest of the user interface. By the way, we have create two new stereotypes based in CKEditor. The first is SIMPLE_HTML_TEXT: That is, the classic HTML_TEXT editor but with less buttons. We also have a completely new stereotype, DISCUSSION. To use it just annotate a String property with the stereotype, thus:

And you'll get a complete discussion thread associated to your entity: This allows you not just to create applications such as forums, blogs or trackers with OpenXava, but also adding some social flavor to your traditional business application.

Partial condition in baseCondition @Tab

Until now you had two options for baseCondition: putting the condition to put after the WHERE or writing the complete SELECT. The complete SELECT does not work very fine with user columns customizations and the condition after WHERE is very limiting. Since v5.6 you have a third option that is to write the JPQL sentence from the FROM clause. To do it just start the baseCondition from FROM, in this way: