Saltcorn 0.3.0 is one of the largest releases so far, almost a month in the making. With this release, your favourite open source no-code platform takes a big step forward and is now adequate for a large portion of the kinds of sites typically built with other nocode platforms.
- Actions: actions can be triggered in response to row changes in tables, buttons can be configured to trigger actions, or actions can be run periodically. Actions can be supplied by plug-ins and are configured with the nocode interface. Some built-in actions are:
- Web hook: make a request to a URL. If the action is triggered by a row, the request payload can include the row
- insert joined row: insert a row in a join table. This can be used to implement likes and ratings.
- Per role theme: you can now install multiple themes and set a different theme for each user role.
- Config: when running the multi-tenancy system, some users reported that some configuration values needed to be shared between different tenants. It is now possible to either fix configuration values in the on-disk configuration file, or to declare that some configuration values are inherited from the root tenant to subdomain tenants
- Container: there is more flexibility in configuring the layout of container elements. These can also now be shown or hidden depending on row values or user roles
- Submenus: user-defined menus can now have submenus. We use the jQuery-Menu-Editor library to edit the menu
- In-app upgrade: running Saltcorn instances can now be upgraded to a new version of Saltcorn by the administrator under the admin menu. This only works if you have installed Saltcorn as the user under which the system is running. We have updated our installation instructions to reflect this procedure. If you are running Saltcorn under Docker, you must upgrade your containers instead of running the in-app upgrade
- Filter joined: you can now filter on join tables, both on child and parent relations. To see an example of this, I updated the open source nocode directory to allow you to filter on the tool type.
- Search improvements: global full-text search results are now paginated, enjoy better separation and can be restricted to one table only
With this release, we have now covered many of the most important steps in the roadmap. The next development cycle will therefore focus on usability improvements and better plugins and themes. One upcoming larger change is the implementation of a pluggable authentication system, so identity and two-factor authentication can be delegated to plug-ins which may implement a variety of mechanisms for authentication.