Skip to content

Releases: moqui/moqui-runtime

Moqui Runtime 3.0.0

31 May 19:04
6eaeeed
Compare
Choose a tag to compare

Release 3.0.0 - 31 May 2022

Moqui Runtime 3.0.0 is a major new feature and bug fix release with some changes that are not backward compatible,
in parallel with the release of Moqui Framework.

In this release there is a new render mode (qvt) and apps screen wrapper (/qapps) that is like vuet and /vapps but uses
the Quasar project, a Vue JS component library based on Google Material Design. The new Vue JS component library in Moqui
(in WebrootVue.qvt.js) takes a big step toward more client rendering and better use of Vue JS components and events,
making it far easier to extend with dynamic behavior (vs the vuet and html render modes).

There are various small improvements to the System and Tools apps, and some new screens like an interactive Groovy Shell
screen and a Table Stats screen that shows the number of records in each entity's table.

This is a brief summary of the changes since the last release, for a complete list see the commit log:

v2.1.3...v3.0.0

Non Backward Compatible Changes

  • Two transitions were removed from the rest.xml screen (/rest):
    • moquiSessionToken: for security reasons, it opened a vector in a CSRF attack to acquire the session token at any time
    • api_key: there is no good use case, just use cases that are less secure and poorly thought through

New Features

  • MFA support for login and update password in screens and REST API with factors including authc code by email and SMS,
    TOTP code (via authenticator app), backup codes; can set a flag on UserGroup to require second factor for all users in
    the group, and if any user has any additional factor enable then a second factor will be required
  • Saved Find dialog (in form-list) improvements to show options for scheduled screen render, to send regular reports to
    users by email (simple email with CSV or XSLT attachment)
  • Groovy Shell screen added to the Tools app (with special permission), an interactive Groovy Console for testing in
    various environments and for fixing certain production issues
  • Update Swagger UI to 4.1.3 with JS/CSS files loaded from cdnjs instead of locally to avoid having files in the repos
    making it easier to update over time, along with cleaning up an old mess and a few CVE and WS security issues

Moqui Runtime 2.1.3

07 Dec 15:50
Compare
Choose a tag to compare

Moqui Runtime 2.1.2 is a patch level new feature and bug fix release, in parallel with the release of Moqui Framework.

There are only minor changes and fixes in this release. For a complete list of changes see:

v2.1.2...v2.1.3

Moqui Runtime 2.1.2

23 Jul 19:11
Compare
Choose a tag to compare

Moqui Runtime 2.1.2 is a patch level new feature and bug fix release, in parallel with the release of Moqui Framework.

This release includes JavaScript library updates including Bootstrap 3.4.1, jQuery 3.4.1, jsTree 3.3.8, Moment.js 2.24.0, and Vue JS 2.6.10. This was done mainly for security reasons and updates to JS code in this repository have been done to fix issues from the updates.

There are various improvements to System and Tools app screens for usability and to better handle larger databases.

There are only minor changes and fixes in this release. For a complete list of changes see:

v2.1.1...v2.1.2

Moqui Runtime 2.1.1

30 Nov 00:17
Compare
Choose a tag to compare

Moqui Runtime 2.1.1 is a patch level new feature and bug fix release, in parallel with the release of Moqui Framework.

In this release there are significant refinements and fixes for the Vue JS based vuet/vapps mode and it is now the default (ie default under webroot is /vapps instead of /apps). The standard HTML mode is still available under /apps and there are still links to switch on the app list screen. There is also now support for Vue component based XML Screens using a .js file and optional .vuet file that gets merged into the Vue component as the template. For an example see the DynamicExampleItems.xml screen in the example component.

Moqui has an improved look and feel with simplified and less cluttered CSS styling. These changes are implemented as overrides in a section at the bottom of webroot-theme.css so they can be easily changed or overridden.

QZ Tray is now supported (only in vuet mode, QZ connection maintained across screens) with a print options dialog in the header. Screens can use QZ Tray in custom JavaScript to print, communicate with devices, etc.

Various screens in the System and Tools apps have been improved and modernized using newer XML Form functionality. There are also some improvements to work better in vuet/vapps mode (now the default).

HTML and JavaScript generated for html and vuet render modes has a few output encoding fixes which fixes the rendering of screens in various conditions (especially under vuet) for HTML and JS reserved characters, and for XSS mitigation.

See the complete release notes at:

https://github.com/moqui/moqui-runtime/blob/master/ReleaseNotes.md

Moqui Runtime 2.1.0

22 Oct 23:28
Compare
Choose a tag to compare

Moqui Runtime 2.1.0 is a minor new feature and bug fix release, in parallel with the release of Moqui Framework.

This release introduces the new 'vuet' render mode for applications that uses a Vue JS based single-page application shell and supports hybrid client/server HTML rendering. The Vue shell (router, etc) is accessible on /vapps while the server rendered HTML is still on /apps. The benefit is a significantly better user experience with existing XML Screens and a foundation for fully client-rendered screens for dynamic in-browser interactivity. Even with hybrid client/server rendering using XML Screens page loads are faster and there is less load on the server, along with better error handling and improved widgets (user interface elements).

See the complete release notes at:

https://github.com/moqui/moqui-runtime/blob/master/ReleaseNotes.md

Moqui Runtime 2.0.0

25 Nov 03:56
Compare
Choose a tag to compare

Moqui Runtime 2.0.0 is a major new feature and bug fix release, in parallel with the release of Moqui Framework.

In this version the CSS and JS libraries used are significantly simplified and refined, along with JS and CSS for cleanups and workarounds in widgets and styling (including layout, etc).

XML list forms (form-list) have been improved in various ways to make it a functional reporting tools with various options to parameterize reports and support light user customization of reports including column layout configuration, saved finds, etc.

There are various new System and Tools app screens for system status details, multi-instance management, service job admin and history, seeing active users summary, database snapshots, and query statistics.

Moqui Runtime 2.0.0 RC1

06 Nov 00:02
Compare
Choose a tag to compare
Pre-release

This is a release candidate for public review. See the release notes at:

https://github.com/moqui/moqui-runtime/blob/master/ReleaseNotes.md

Moqui Runtime 1.6.2

26 Mar 22:18
Compare
Choose a tag to compare

Moqui Runtime 1.6.2 is a minor new feature and bug fix release, in parallel
with the release of Moqui Framework.

New Features

  • New Moqui logo!
  • Removed example component, now in a separate repository (moqui/example)
  • Many unused JS libraries removed (from webroot/assets/lib directory)
  • The Tools app can now be run in Tenant instances, with the entities in
    the tenantcommon group excluded from various screens
  • The Resource ElFinder screen in the System app now restricts access to
    file and classpath resources for all tenants except DEFAULT
  • Added basic tenant admin screens, only accessible in the DEFAULT tenant

Moqui Runtime 1.6.1

25 Jan 05:42
Compare
Choose a tag to compare

Moqui Runtime 1.6.1 is the first release of the runtime repository separate from the rest of Moqui Framework.

Version numbers of this repository will match those of moqui-framework, the two are developed in parallel. They are separate to make it easier to use your runtime directory separate from the rest of the framework (for configuration, custom UI, etc). The easiest way to do this is generally to fork from this repository (moqui/moqui-runtime).