Articles 2024-01-282023-11-202023-09-062023-06-192023-04-032023-02-072022-12-302022-10-07
New platform version, 2024-01-28

Release of REI3.7

We´re back in 2024 with a new feature release, REI3.7 - let´s have a look!

Custom translations and caption maps

While REI3 always supported multi-language applications, authors had to provide and keep languages up-to-date. This now changes. In REI3.7, any admin can add new languages to existing applications and provide their own translations. Even better, these custom translations can then be exported, shared and imported by the original application author, if they want to officially support a language.

Custom translations are done in the admin panel with our new 'caption map', a overview of all titles, labels, help texts and so on. This caption map is also available inside the Builder for application authors to check and correct translated values from all parts of their applications.

Many days of work have gone into this feature. We hope that it provides a lot of value.

Triggers on steroids

Relation triggers are a very powerful tool, used to execute changes, apply business logic or limit actions. But they always had a key limitiation: They could only work within their own application.

With REI3.7, we´ve reworked triggers so that they can react to changes in built-on applications. This means that you can not only expand existing applications with data and user interfaces, but also apply your own rules & events. If something changes in another application, you can easily react to it with a trigger and then create a task or send a notification - or even block the action if you have a reason for it.

To create a trigger for a relation in another application, you create a new backend function of the type 'trigger' and then assign the trigger inside the new function.

Field sizing changes

The REI3 form layout engine is optimized for allowing large amounts of input fields on very different screen sizes. Because of this, sizing is done not for each field individually but for entire rows or columns. This works very well for horizontal sizing, but while some fields can easily grow vertically, many look off when not correctly sized.

Before this release, fields would take both horizontal as well as vertical size from their parents and grow automatically. In REI3.7, we´ve changed that behaviour so that only fields that benefit from vertical growth, actually do grow. This is a breaking change that does have some drawbacks, mostly that there is less control in how fields are sized and that some existing forms will look different after the change. However, in the vast amount of cases, it should make building forms easier and make unoptimized layouts look better, as vertical sizing does not need to be configured for many fields.

This is not a change we did lightly but we believe the benefits are much larger than the drawbacks. We hope you agree.

OAuth2 support for mailing

Many organizations running REI3, use cloud-services such as Office365 for mailing. We´ve now added the ability to register REI3 as an OAuth2 client, which can be used for authentication in email accounts. Templates for O365 are offered in the admin panel, a short guide on how setup works on the provider side is also available.

Redesigned application cache

We´ve redesigned the way REI3 manages application caches so that much less data needs to be reloaded and sent to clients when changes are done or updates are installed. This results in less bandwidth required and shorter loading times when working in the Builder. This also speeds up access to an updated REI3 instance on a mobile connection.

And more shiny things

  • With OAuth2 clients and expiring secrets, we´ve felt the need to add a notification system for admin contacts. It will send out email notifications when important system events occur. For now, it will react to upcoming expiration of OAuth2 clients and system licenses.
  • When sorting list batched columns, all column values are now used to sort with. Before, only the first valid column value would be used.
  • The REI3 platform can now apply proxy settings for update checks, repository updates and application downloads.
  • A new frontend function allows expert authors to apply custom ECharts options to chart fields. With this, authors are not limited by what options REI3 supports and can use all features of the ECharts library.
  • PDF files can now be uploaded to file inputs after creation. This option is available in the 'pdf_create()' frontend function and skips the document download that is otherwise offered.
  • For new installations, the integrated database engine is now Postgres 16.1 (standalone/portable deployments only). Existing installations will stay with the older version (Postgres 13.7) as we cannot safely automate the upgrade process. Because the integrated database engine is only used by REI3 and fulfills all requirements, an update is optional. A manual upgrade is possible and can improve system performance.
  • Reworked the user interface for the application management page in the admin panel.
  • ... and many more small fixes and improvements.

Upgrade notes

This release does not need any special upgrade steps.

  • On Windows: Run the installer.
  • On Linux systems: Stop the service, extract the latest release, replace the r3 binary, start the service.

Thank you all for your continued support and feedback. For the full list of changes, take a look at the technical change log.

New platform version, 2023-11-20

Release of REI3.6

We are happy to announce that the next major release, REI3.6, is now ready. This release is a bit different then the last ones, focussing mostly on visuals and usability.

Buckets of fresh paint

With many new features and capabilities being added to REI3 over the years, its not been easy keeping a consistent look & feel. Some user interfaces have not been updated since 2020. We´ve postponed work on these things in the past to focus on features. But it was time to take a swing at it as feedback regarding our outdated interfaces grew louder.

This brings us to REI3.6. We put in many hours to redesign, update, test and generally make all visual elements more consistent. Here are some before and after screenshots:

We´ve also redesigned the login page:

... as well as some outdated Builder interfaces, like the roles UI:

Many changes cannot easily be shown with screenshots as they need to be felt. Relationship inputs are now much easier to use, especially on mobile devices. Calendar & Gantt fields were updated to be easier to read and use. Lists field now dynamically shrink and replace their actions and inputs, based on the available screen space, allowing for easier to access inputs in many cases. Many context dependent actions (like CSV imports or complex filters) were moved to their own hover menus, making interacting easier as well.

These and many more changes made it into REI3.6. We hope you like the new designs as much as we do.

Updated user options

We´ve always had many options to adjust the REI3 interface to each user´s preference. With the redesign of REI3.6, we had to cut some options, but added more.

For example, users can now customize, how lists are displayed:

They can also overwrite header & menu colors as well as choose decimal number separators.

They can also go back to some of the looks of older REI3 versions, if they prefer:

Widgets & customizable home page

Widgets allow application authors to provide small, useful forms or shortcuts for users to add to their home page. There is little new to learn, as form widgets work the same as regular forms - they are just smaller.

We´ve updated some of the applications in the repository to demonstrate possible use cases. Like list widgets showing pinned tasks, favorite tickets or a widget that allows for quick time tracking.

When migrating to REI3.6, each users home page will be filled with widgets showing application shortcuts that look very similar to how REI3 used to look. The difference now is, that users have control over these and can choose what to keep and how to arrange it.

Drawing inputs

We started with the need for a signature pad, but while looking at implementation options, we´ve decided to expand the feature a bit. Now in REI3.6, authors can add so called 'drawing inputs' - these can be used as signature pads, but just as well for meeting notes or small drawings.

When used as signature pad, a small drawing input is placed on the form and then set to readonly after save. Inside the data are both the drawing data (which can be updated later if desired) as well as a PNG version of the drawing, which can be sent via e-mail or placed in a PDF file.

This feature is not a replacement for visualization tools and is not meant to create complex drawings. But it comes with some basic tools to support different use cases, such as stroke options, zoom and panning.

More new stuff & improvements

  • Menu entries can now be colored, to help users easily navigate different areas of your application.
  • List and tab fields now also have their own field titles. This is mostly useful for smaller list/tab fields that need description.
  • The new login page now offers a range of background images, which can be configured in the admin panel. The old login background can also be re-enabled if desired.
  • Datetime inputs can now be toggled between month/week views.
  • List views can now be toggled by users between table and card layout for every list.
  • The Builder interface for form functions now includes context help to explain how and when form events trigger assigned functions.
  • The feedback dialog was updated to give more details how and where feedback is being sent. It now also includes details for system admins on how to configure the feature.
  • A new application navigation menu has been designed for mobile devices but can also be enabled in desktop mode, by switching off application menu entries in the user settings.
  • Some more customization options were added:
    • The option to 'stay logged in' can now be disabled.
    • The login background image can be overwritten.

Of course, this release also includes a range of bug fixes.

Upgrade notes

This release does not need any special upgrade steps.

  • On Windows: Run the installer.
  • On Linux systems: Stop the service, extract the latest release, replace the r3 binary, start the service.

Thank you all for your continued support and feedback. For the full list of changes, take a look at the technical change log.

New platform version, 2023-09-06

Release of REI3.5

Another release! REI3.5 is out with lots of new features, starting with...

Kanban fields

With the new Kanban fields, your data can be shown and managed as cards on a Kanban board. Easily view and then assign things to people, states or whatever you can think of.

Besides the classic Kanban layout, REI3.5 also supports two-dimensional boards, enabling fast multi-value assignment.

Just like lists or calendars, Kanban fields support the full range of filter options, from filter sets to collection inputs.

New calendar views

With REI3.5, users can now switch to 1-day, 3-day, work week and full week views in calendar fields. Especially relevant for partial day event planning, the new views greatly improve usability when working with calendar data.

Besides calendar fields, the new views are also used for date inputs. We also added a simple drag-to-input date selection feature to further speed up record creation.

Label fields

We´ve replaced the existing header fields with a new, extended version. Now called 'Label fields', these offer full HTML content on forms. Either via the richtext editor or directly with raw HTML, you can now add formatted text, images and other content to your forms.

The content of label fields is also specific to the current user language, enabling translatable context help with lots of styling options.

Dedicated mail traffic log

Useful for systems dealing with a lot of mail traffic: In REI3.5, every in- or outgoing message is being logged in a dedicated mail traffic log. In addition to the existing mail service logging, this feature provides a quick overview of mail traffic, regardless of system log settings.

Better handling of frontend functions

Frontend functions also got some love with this release. Instead of jumping back and forth through the Builder, frontend functions can now directly be created from where they´re needed. With contextual shortcuts and pre-filled inputs, creating a frontend function should be significantly faster.

Additionally, frontend function names now only need to be unique within their assigned form. No need to use prefixes for similar functions on different forms. The Builder UIs also have been updated to better show where frontend functions are used.

More new stuff & fixes

  • Forms can now define a field that should receive focus on load, helping with fast record creation. If a form does not have a defined field, the first available input field will be set active.
  • Icons and context help has been added to the container field options, to help better explain layout options.
  • CSV exports now use the translated column titles, if available. If not, they fallback to attribute titles and ultimately to attribute names, if nothing is else is available.
  • Added more instance functions: You can now overwrite the form title, close a form or change a field focus within frontend functions.
  • Cleaned up the log view in the admin panel.
  • Forms can now be opened with relations other than the base relation. This removes the need to recreate things like list fields, when a wrong base relation was chosen. It can also simplify some queries, as the base relation does not need to be the one used for opening forms.
  • Fixed iFrame fields not behaving correctly if opened while being invisible (inside hidden field/tab).
  • Fixed an issue with the integrated backup, which would fail if the database name did not match the database user name.
  • Fixed bulk edit options not being available if the delete option was disabled on a relation.
  • Fixed boolean values in column filters being shown as true/false.
  • Fixed colors being too dim in dark mode.

Upgrade notes

This release does not need any special upgrade steps.

  • On Windows: Run the installer.
  • On Linux systems: Stop the service, extract the latest release, replace the r3 binary, start the service.

Thank you all for your continued support and feedback. For the full list of changes, take a look at the technical change log.

New platform version, 2023-06-19

Release of REI3.4

Its that time again - a new major update for REI3 is out, so let´s see what we got.

REST calls

Although REI3 could already offer APIs as a REST server, sending or pulling data from inside your REI3 apps was not supported. With REI3.4 we can now execute REST calls directly from backend functions. This enables regular data exchange based on schedules or event based updates via triggers or other function calls.

Because every REST API is different, you can freely define headers, request bodies and so on. A REST spooler attempts to execute your calls even when there is a temporary issue.

Function templates

REI3 offers a lot of freedom when it comes to functions and data processing - having a lot of options however inevitably leads to complexity. Especially with the new REST calls, we´ve found that there are so many ways to do things that regular documentation just was not practical.

So we decided to build function templates for the most common use cases. When attempting to build complex functions, templates can help you get started. Besides templates for REST calls, we´ve also added one for processing incoming mails from the mail spooler. Depending on feedback and how future features will look, we will extend the number of templates.

Bulk update forms

Introducing: Easily update hundreds of records at once directly through a list with our new bulk update forms. With REI3.4 you can assign a bulk update form to any list.

By default every field on a bulk update form is optional and only values of changed fields are updated. This just makes sense as you might not want to change certain values at all. But you can however still use form states to dynamically change this behavior, to make certain inputs mandatory for example.

Bulk update forms can be assigned in addition to existing forms, so you can open a specific record on one form, while using a another, simpler form for mass updating specific values.

Inline forms

Up until now, you could open records either directly (as a new page) or as a floating window. Now we have a third option - the inline form:

Especially useful for records with few inputs, the inline form keeps everything visible while you can create or update your record. Bulk update forms can also be opened as inline form.

Besides lists, calendar & Gantt fields also support this feature:

Inline forms generally need more space to work, so they are automatically converted to floating windows when using a mobile device.

Direct app access

There are many reasons, why you might want to directly open a specific app instead of the start page of the REI3 instance. Maybe your users only use one app - or maybe you want to install multiple apps on your mobile devices individually. This is now possible via direct app access.

With access to customizing, you can now define individual apps, that can be accessed and installed individually. They are then shown as native apps on devices and can have their own title and icons. It does require sub domains and a wildcard certificate to work correctly however. But if your infrastructure supports it, this can make your apps feel even better than before.

Easier column batching

Batching columns together never was quite intuitive, with a batch number you had to assign and which had to match columns around it. With 3.4 we´ve redesigned the interface so that you can just drag and drop columns to create column batches.

More column options

In addition to easier column batching, you can now set some styles for your columns. When batching at least 2 columns, you can now also choose for your content to be vertically aligned - this means that lists like this are now possible:

iframe fields

Useful for integrating external resources, iframe fields are now available to access anything your browser can display.

Because iframe fields just show what value you assign to them, you can dynamically update a URL with getter parameters to show context specific resources. You can also simply use a default value on a readonly iframe field to provide access to an intranet login page.

Custom CSS

Don´t like how REI3 looks? No problem - with new customizing options in REI3.4, you can provide your own custom CSS. Make buttons rounder, colors pop or change styles as you desire.

Text indexing

We knew for a while that our regular indexing did not support larger text values. This was causing us headaches with apps we designed, especially in regards to our knowledge base and ticket system.

The plan was to address text indexing a while back... but we found that it was a more complex issue than we had anticipated. Besides that, solving text indexing would also enable other powerful new features. So the scope increased and it took a while to get it done. But here we are.

REI3 now offers a simple to use text index option that can be selected when creating new indexes. It only supports text values (obviously) and works on a single attribute. But when its enabled, the system can now find records over hundreds of thousands of large texts within milliseconds. And that is not all.

Together with very fast lookups, REI3 now also offers full-text search (FTS) capabilities for values that have a text-index. This means that you can scan for words or phrases, like you would googling something online. And even better: If you can know the language of a text, the full-text search can use language-specific features to improve your search even more, like looking for results with the same word stem. For this you need the new 'dictionary attribute' to select and store the appropriate language value of a text.

Text indexing is not something you will need for every app - but if you need it, these features will make things much better.

Some more things

  • When creating a new child record via a list or calendar field, n:m fields can now also be populated.
  • PWA options such as app title and icons are now available for individual applications.
  • The customizing UI in the admin panel has been redesigned, including more options & context help.
  • Relationship inputs in the Builder for n:m now use unique icons to differentiate themselves from other types.

Duplicate primary key references

REI3.2 introduced a bug in which applications being newly imported into another instance would duplicate index references for primary keys. Luckily this caused no issues besides looking weird. This bug is now fixed. To remove duplicate entries, have all affected applications in a REI3 instance <3.4 and then upgrade to 3.4 - duplicate indexes will be removed and you can re-export your applications.

Upgrade notes

REI3.4 does not need any special upgrade steps.

  • On Windows: Run the installer.
  • On Linux systems: Stop the service, extract the latest release, replace the r3 binary, start the service.

Thank you all for your continued support and feedback. For the full list of changes, take a look at the technical change log.

New platform version, 2023-04-03

Release of REI3.3

A new major update to REI3 is here with loads of new features & improvements. Let´s take a look.

APIs are here

With APIs (or Application Programming Interfaces) you can create, update and delete records. Any system, tool or script can now be connected with REI3 by simply executing REST calls. And the best part: All the features you know already still work as before. Some examples:

  • Do you have business logic for record updates? It does not matter if you use forms or an API, the same triggers and backend functions will execute.
  • Roles and relation policies that give or restrict access? Also apply to APIs.
  • Getting or updating records from multiple relations? Nothing new to learn here - works as before.

Also nice: If you need to make changes to your REST calls, you create a new API version with a single click and make changes to the new version instead. This way, you can make changes to your APIs while older calls still run as before.

APIs are important in many scenarios and we are happy to offer this feature now as a standard.

New attribute management

Every low-code or no-code tool needs to decide how much to abstract away to keep things simple. With REI3 we decided to use the least amount of abstraction, to allow authors to be flexible and build powerful applications; this is why attributes in REI3 always were quite technical.

With REI3.3 we looked at how we can make the life of application authors easier for the most common use cases, without loosing power and flexibility. So now with this release, we introduce 'attribute value types'.

Instead of choosing an attribute´s content (like integer, bigint, real, etc.) you now choose what your attribute values are going to be used for. Be it text, decimal numbers, dates or colors. REI3 will then offer you contextual options depending on your chosen value type.

In the same way, your frontend components (forms, fields, lists, etc.) can now automatically adjust their presentation without any additional inputs. Some display options are still there for edge cases, but overall it should take less time building your applications.

A new look

A friendly request in our new REI3 Community Forum suggested that we update our user interface towards a specific look. At first we were hesitant to add a such big change to an already large feature release - but then we got curious, and found we could actually implement this suggestion without much issue. So here we are now:

As the feedback from our testers was overwhelmingly positive, we decided to make it the default. The old look can be enabled by toggling 'Field backgrounds' in the user settings, for those who prefer it.

Tab counters

We introduced tabs with REI3.2 and found very quickly, that they help facilitate user-friendly and nicer-looking forms. So much so, that we ourselves can´t stop using them everyhwere. Putting more stuff in tabs has a downside however. A no-brainer in hindsight, the more we use tabs, the more we make stuff invisible as only one tab is ever active at the same time.

To mitigate this new issue, with REI3.3 you can now enable counters for each tab. A tab counter will show how many records are shown in lists & calendars or how many files are attached to a file input inside a tab.

This feature requires more performance, as even invisible fields and records must be processed to update the tab counters. You can decide where having counters is sensible and activate the option accordingly.

More Builder improvements

The Builder has again received some love. Following the new attribute value types (s. above), corresponding value type icons are now shown in many Builder interfaces.

This makes it easy to see, what you are dealing with. We found it especially useful in regards to relationships.

Speaking of which, the relation management interface for data queries has been reworked as well. Much cleaner and nicer looking (at least we think so), it is now easier than ever to see what relations are joined, what settings are active and what relationships are used.

Easier access to input fields

In large data forms, it can sometimes get difficult to find the one input field that you are looking for. REI3.3 introduces a new way to access data input fields without having to find them inside the form layout. Just choose 'edit fields' in the right panel and a list of all input fields can be accessed directly.

New login management interface

The login management user interface has not changed much since the first public release of REI3 many years ago. With more features coming over time it became harder to update - so we redesigned it.

It should be easier to use for admins as well as easier to add new features to in the future.

Login templates

This feature enables admins to set defaults for user settings, like the active language, region or display options. Login templates can be chosen at login creation or assigned to LDAP connections.

Improved list colors

A small but very welcome feature: List columns will now be filled by a background color if any color attribute is part of a column batch. Text color is automatically adjusted to contrast well with the column background to keep things readable regardless of chosen color.

Improved backend function editor

With the increasing number of options for the function editors, we had to streamline quite a bit to fit all options. For the backend function editor, the user interface became nice to look at, but time-consuming to use - especially when you needed to use many relation or attribute placeholders. With REI3.3 we reworked the UI again to give you very quick access to placeholders within the current context.

More help for new application authors

REI3 never was the easiest low-code tool to work with - but that does not stop us from making it easier with time. In this release we´ve added a 'first steps' page, which helps new application authors get up and running and avoid common mistakes.

We´ve also also added contextual warnings for common failings, like missing attributes in sub queries or undefined base relations for list views. We aim to further improve the usability of REI3 without loosing functionality.

Even more new things

  • New attribute type: Universally unique identifier (UUID). Very useful for data exchange between disconnected systems.
  • New date & time filter options. It is now very easy to filter for records changed in the last 3 days for example.
  • New form state condition 'field is valid' - you can now change your form depending on the validity of field inputs.
  • Directly execute backend functions from inside the Builder. Very useful for testing your functions.
  • Collection filters are now persistent during navigation - filtering for categories or tags is now kept just like any other filter.
  • File inputs now show placeholders for file types if no thumbnail is available.
  • New user option for always returning to the last active tab on a form.
  • Presets can now be referenced in front- & backend functions directly via instance calls.
  • Form state conditions can now be filtered by affected tabs.
  • Custom field error messages are now available, which you can set with frontend functions.
  • Removed the need to load list fields if they are not visible. Saves performance and bandwidth.
  • System captions are now loaded as cachable files - this results in less data needing to be loaded after login.
  • You can now reference presets from built-on applications in filters and form state conditions.

Upgrade notes

REI3.3 does not need any special upgrade steps.

  • On Windows: Run the installer.
  • On Linux systems: Extract the latest release and replace the r3 binary.

This turned out to be our largest release yet. Thank you all for your continued support and feedback. For the full list of changes, take a look at the technical change log.

Official REI3 forum, 2023-02-07

REI3 community forum

We are happy to announce that the official REI3 community forum is now live.

So far, people reached out to us via email, Github and our contact form. With this new forum system, requests can be seen and answered not just by us, but by all participants.

How to use it

We kept it as simple as possible - just go to, choose your preferred username and confirm your account via email. Then you are in and ready to post.

This system is new, starting with basic categories and tags - we will use it for everything community related and expand as we go on.

Thank you for the time and effort you have shown us - we hope the new system works well for everybody.

New platform version, 2022-12-30

Release of REI3.2

Today we release a new major version, REI3.2. This release includes a long list of features, improvements and fixes, so let´s jump right into it.

Tab fields

For larger forms that struggle to contain all their inputs, fields can now be placed in tabs. The new tab field can contain multiple named tabs, which each can contain as many fields as desired. With container fields and nested tabs, even complex layouts are possible within tabs.

Tab fields come with many usability features. For one, they are marked if any required input is hidden within a tab and the record could not be saved. Additionally, tabs themselves can be hidden and managed via form states.

When a single input field is placed inside a tab, it will take all available space, making it feel seemless.

Multi-factor-authentication (MFA)

With REI3.2, users can increase their account security by adding an additional authentication factor to their account. Register an authenticator app by scanning a barcode in your user settings and your good to go. Any modern authenticator app can be used that supports TOTP, like Microsoft or Google Authenticator.

To protect against loosing access, multiple authenticators/devices can be added. If nothing else works, an REI3 administrator can reset your multi-factor-authentication.

Redesigned Builder

We´ve been adding new features to the Builder for years now, finding it harder and harder to stuff them into the existing user interfaces. Sometimes this caused the UI to suffer...

This had to change at some point. This point is now. We went a little nuts and reworked most user interfaces in the Builder. New navigation, new entry points, loads of moving stuff around and so on. It will take a bit of time to get used to, but we are very happy with the results.

Especially the form editor now keeps the important form layout as is, while form states, functions, field options and form properties stay in the sidebar.

Flexible help articles

Something for the good people updating documentation: You can now create help articles that are reusable in different contexts. Instead of creating a large documentation and copying parts of it to different form context help pages, you can now create short articles and assign them to the main application help or to multiple forms.

Articles can be placed in any desired order - with a table of content automatically being generated if more than 1 article is available. You can even reuse articles from applications that you build on.

Better integrated backups

We´ve had integrated backups for some time for smaller stand-alone systems running on Windows. With REI3.2 we now support other environments as well, allowing integrated backups to run on non-stand-alone instances, on Linux, on ARM systems or wherever you run REI3 from. The only requirement is that you have the Postgres client utilities installed on the REI3 server (for database backups).

Additionally, you can now view existing backup sets inside the admin user interface.

Upgrade notes

REI3.2 does not need any special upgrade steps.

  • On Windows: Run the installer.
  • On Linux systems: Extract the latest release and replace the r3 binary.

For integrated backups on Linux systems, make sure to install the Postgres client utilities, such as:
apt-get install postgresql-client

Small fixes and improvements

  • List filters are now cached for the user session, meaning they stay active when returning to a form.
  • Collection values shown in the header, are now combined into a notification bell on mobile devices.
  • Collection values are now updated when assigning records (like a contact) to a login. This makes a page refresh after assignment unnecessary.
  • Improved file inputs, making them take less space by default and show better image galleries.
  • The portable version of REI3 can now be started by just double-clicking the executable. This is enabled by default for new versions. For existing portable versions, add "portable":true' to the config file or continue using the start script.
  • Most database entities (applications, relations, attributes, backend functions) can now have longer names, up to 60 characters (from 32 before).
  • Fixed issue in the form editor where it would not alert the author if a referenced field was deleted.
  • Fixed application import issues that could cause the server to hang or the import to fail in some edge cases.
  • Fixed form state conditions not being always updated by relationship input fields.
  • Fixed CSV export ignoring column filters.
  • Fixed invalid column aggregation being shown after a list was updated in the same instance.
  • Fixed multiple issues with the form copy functions.
  • ... and more smaller fixes and improvements.

That´s it for this release. For the full list of changes, take a look at our change log.

New platform version, 2022-10-07

Release of REI3.1

We are happy to announce that REI3.1 just released. In addition to a redesigned file management, many new functions are included for operators and users of REI3. Please be aware that this version requires an additional upgrade step - read on below for details.

New file management

Until now, file management was a small part of REI3 - good enough to be useful but limited in functionality. This changes now.

Lets start with the new file input: It works as before, allowing you to easily attach files to any record; but it can now also grow and support much larger file sets. Including options for sorting, filtering and copying files - the new file input makes it possible to handle many more files at once.

We also got a new client application to support quick and easy access to files from within REI3. After setting up the app (on Windows, Linux or MacOS), it syncs to the REI3 server and receives requests to open files on your local computer. You can then directly work on your files, save your changes and the client will sync everything back

Additionally, application authors can now parse files and also create hardlinks to them, allowing access to the same files in different contexts.

We plan to release a file management application on the platform to enable teams to work on REI3 files together. In the meantime, authors can use the new features to build stronger file management into their own applications.

Column filters & aggregators

A small but universal feature: Users can now select filters based on all values within a list column. Together with a redesigned column management UI, these filters will be available on all lists automatically. Additionally, aggregation functions can also be used to build sums, averages and so on.

Builder improvements

The Builder has received some love as well. Interfaces that handle single entities (like forms, functions or roles) can now use the CTRL+S hotkey to save changes. In general, actions in the Builder have been redesigned to be more consistent with other UIs.

As a safety feature, the Builder now automatically defaults to a read-only mode for applications from other authors. You can still change these applications by disabling read-only mode inside the applications panel in the admin UI. As before: You can build on other´s applications safely; but direct changes to these applications are overwritten when a new version is installed.

ARM64 support

Get your Raspberry Pis out - REI3 now officially supports ARM64 processors on Linux systems. Requirements and installation steps are the same as for any other Linux operating system. For more details, check out our admin documentation.

Upgrade notes

REI3.1 can now create thumbnails for common file types, including images and PDFs.

Windows releases include most dependencies, but Ghostscript must be installed separately on the server for PDF support.

On Linux systems, both ImageMagick (for images/text files) as well as Ghostscript (for PDFs) must be installed separately. This can be done on most systems with the included package manager, such as:
apt install imagemagick ghostscript

Small fixes and improvements

  • Large lists now scroll their content instead of the entire form.
  • Multiple new messages and warnings help authors but also admins to avoid common mistakes.
  • Platform logs were cleaned up and are now in color.
  • Expert filters are now also available in smaller fields given the field size is sufficient.
  • Fixed an edge case, in which PWA do not reload their cache, when the server is updated. Hopefully, after 3.1, you never need to manuelly reload your browser cache again.

For the full list of changes, take a look at our change log.