Release Notes


  • Our Mail Alert section has been cleaned up with all the redundant options now removed when adding or editing mail alerts.
  • For all new fields created from this version onwards, if a field is being used by any rule or field parameter it is not possible to delete it without first editing or changing the parameter or rule first. This adds more stability to your no-code builds and creates more predictable behaviour.
  • Fixed a Maths field bug where an infinite loop was being caused by a red alert rule warning.
  • Removed the pop up warning when editing blocs that already have data. This has proved unpopular and had been ignored by builders.
  • Upgraded our main Framework and code language version.
Release Notes


  • Resolved issue where an Auto Generate Reference field (the field that can be used to count against) was triggering a new autogeneration while editing a record
  • Changed wording/typo in a field name
  • Cleaned up the list of roles when there are multiples of 2 in the Manage Roles section
  • New Maths field updates to allow min(), max(), round() and avg() and more to come soon
  • Fixed bug where on new versions, any new text on the front end requires a log out and log back in for it to appear
  • Fixed small issue issue where the same setting could be seen twice in the Edit Theme section
  • Fixed a bug where when a rule breaks on the maths field it causes an infinite loop of the rule breaking over and over.
  • Added new option to the Cross Bloc Data Manipulator field where you can unset the Condition section to “No Conditions Required”, thus reducing confusion and improving UX.
Release Notes


  • It’s now possible to add multiple search filters/criteria for our Results Box field. Where previously the look up could only match one field, now you can search multiple fields in the other bloc that must match multiple fields in the bloc the Results Box is being created in.
  • There is a new feature where you can disable a user, i.e. make them inactive, this will prevent them from being able to login. This is useful for staff leaving etc but where there is data associated with them.
  • Fixed a small bug where when editing a page, the icon pop up was being visually blocked.
  • A major new and useful update to our Mail Alert field, where you can now attach the .docx templates you may have built in that bloc.
  • There is a new feature where blocs cannot be deleted if they are associated with field parameters or rules.
  • A new feature where you can see all the schedules running in your system in the Manage Data section.
  • A new field parameter that allows you to load data from other blocs based on a search criteria. The purpose of this is to allow master lists to always be loaded directly from those lists, as opposed to the data being copied in. This is similar to a JOIN statement in SQL and will allow users to build even cleaner sytems with just one source of truth for their data.
  • Fixed a bug where the File field file name was still visible in the field after submitting. It now clears correctly.

Blocworx Flowcharts

This feature is a useful troubleshooting and process examination tool. It allows for quick handovers of blocs to other people and could even be used to simply design a process.

This currently can be done for each bloc. Coming soon will be the ability to map out your entire system to see how modules, pages and blocs link together.

This will allow people to have an auto-generated sitemap of their software with the click of a button.

Release Notes


  • Major New Update: The Autogenerate field can now be a fully dynamic string with multiple dates in the string and any format of your choosing, not just pre-selected formats. It also now has the ability to include data from other fields, just like our Merge Field.
  • Improvements to our Results Box field to handle various field types like images, file downloads and barcodes.
  • Improvement where the File Builder field and Mail Alert field now has rules/actions called once the button is pressed.
  • Small UX improvements including the Download button at the top of a bloc for templates now reduced in size.
  • Added Improvements and easier access to the user Digital Signature page.
  • More Improvements to our Blocworx Gateway scheduler and the main Bloc scheduler (including internal testing improvements)
  • Improvements and more stable fixes when adding and editing rules.
News & Press

Blocworx 3.0: Welcoming IOT, Scheduling, API Gateways and more

We’ve been hard at work, understanding our customers, understanding ourselves and discovering more and more opportunities with our product. Our work has culminated in features that address the fundamentals of what Blocworx is built for, which is no-code operations and tracking. We established that there were some core solutions that needed to be implemented to make Blocworx the best solution there is available:

  • IOT Compatibility
  • Integration and connectivity of Blocworx
  • Automation and Scheduling
  • Structure and flow, treating no-code like coded work
  • Publicly Available Code and Projects

IOT Compatibility

Recognising the needs for hardware technology and no-code to be increasingly compatible, we are rolling out 3 new fields, the Bluetooth field, an MQTT sender and MQTT broadcaster. We are already live with our Bluetooth field and have the ability to track temperatures from thermometers. We will be constantly adding more and more devices and configurations. The MQTT fields will allow you to connect to any MQTT broker, or a broker provided by us, thus you’ll be able to easily send and receive data to any device over MQTT.

Integration of Blocworx

We are opening up Blocworx, for both data coming in and out. Our new Blocworx Gateway Field allows you to send HTTP requests to any location and work with the response. These requests can be triggered via various means, e.g. a data changing somewhere, or simply using a button, or before you submit your form. This opens up Blocworx and gives you access to an infinite number of APIs, e.g. currency converters, language translators, your own inhouse custom APIs. The launch of the Gateway Field is also done in combination with our new Blocworx API.

Blocworx API

We have launched our API docs for our customers. We will be adding many more endpoints to the docs over the coming weeks. By combining our Gateway field with our API it will be possible for developers to build their own functionality that talks to and reads from Blocworx. This opens Blocworx to be available in any IT infrastructure a company might be using.

Automation and Scheduling

Blocworx has many features and tools, to the point that a citizen developer can get very creative with their solutions to problems. There was one thing missing. To get the best out of Blocworx the processing always had to take place while the user had the screen open and physically interacted with the page. They would build a beautiful process but it was not possible for them to apply the same functionality automatically. We have made a major change to this so now all our features can be accessed via means outside of the Blocworx web application itself.

For example, when someone uploads data using excel, we could apply the rules to the data, call APIs, extract parts of the data and populate other parts, apply Maths data, check for duplicates, populate other blocs with relevant data. All in one upload. We can apply this to any way data gets inputted into Blocworx, either via an API, data upload, or scheduler. Which brings us onto our next new feature. The Blocworx Scheduler:

Manage Bloc Scheduler

Everything described above can now be automated. You could set up a bloc with initial default values and simply begin to create records by themselves. This could be handy for creating audit schedules or even simple reminder systems or stock checking systems using this combined with fields like our Cross Bloc Data Update field and Mail Alert fields.

For example, as a demo, we built a schedule that pulls the latest status from a different bloc of a mechanical tool, this resulted is in being able to give a live graph of uptime of the tool. This was possible using a combinations of simple Blocworx rules and our scheduler.

Structure and Flow

At Blocworx, we take the applications that people build seriously. No-Code by its nature is database driven software, meaning the algorithms and flows that are set out, are determined and held in a database, not immediately in code. While this creates the ultimate flexibility, it can also introduce questions around the resilience of the software. To resolve this Blocworx is introducing a suite of features and solutions that not only address this problem but turn it into an opportunity.

  1. Aside from our existing strong back up regular procedures, we will be introducing bloc restore points in Version 3.2.0. This means you will be able to roll back a bloc you have built. We hope to build on that in the future by having system wide restore points.
  2. We now have the ability to review and troubleshoot your bloc using a Mermaid JS flowchart. If you have built some tools in Blocworx and are beginning to lose track of what you have built or how it works, our flowchart will give you an instant glance of the structure of your bloc. The great news is, because this chart is generated on the fly automatically, you will be able to review all your existing work too, not just new blocs!

Publicly Available Code and Projects

We have built connectors, integrators, Node based Bluetooth Readers and MQTT listeners, auto printing projects, various portals and even simple HTML projects, all of which connect to Blocworx in some manner. We have decided that over the coming weeks we will be making the code for all of these publicly available with documentation. This will allow developers to have out of the box projects waiting that are connected with Blocworx. All of these projects, while completely different to each other, have one thing in common, they are simple code based projects that make use of the power of Blocworx.

Release Notes


  • Added a Sign in with Google feature allowing any business who are with Google to use their own account to log in.
  • Huge improvements to the Blocworx Gateway Field allowing for a wide range of API calling and more options including an automatic scheduler that loops through the records, similar to the Mail Alert scheduler.
  • New Feature: User can now control the actions that occur for any field. The feature is called Manage Field Actions. This feature allows the user to tidy up and control the flow of what happens for each field.
  • New Feature: Ability to put in a custom url with generic parameter style, meaning urls that leave Blocworx can be dynamically generated.
  • Introduction of the Flow Chart: The ability to view your bloc at a glance using a Flow Chart.
  • Major New Feature: The Bloc Scheduler, this feature allows users to automatically run their blocs and all rules, conditions, actions, mail alerts, cross bloc actions can occur automatically on a schedule. There is an option to either loop through existing records, or even create new ones.
  • Excel Uploader Automatic Processing: Using the work complete with the Bloc Scheduler we then added the ability to automatically process a bloc using the Excel Uploader, meaning values can be set, rules can be called and even mail alerts sent when data is getting uploaded.
Release Notes


  • Fixed a bug where sometimes the red error alert was staying visible on the bloc after submitting the form.
  • Created a new feature where the Autogenerate Field can optionally look at the highest number and not necessarily the latest number.
  • Put in place the initial set up for Blocworx Scheduler and Field Actions, thus making a big preparation for Version 3.0
Release Notes


  • Added the ability to change the text on the login page.
  • Improved and fixed bugs in the function where you can quantities to the Date field, allowing you to add days on top of an existing date.
  • Added the ability to change the default empty value from “N/A” to anything you wish (including blank data).
  • Added more frequencies to our Mail Alert scheduler.
  • Fixed a bug where the Multi File field is causing issues with the Mail Alert field.
  • Added a new Bloc parameter, when you leave the bloc you can set a pop up/notification before the user exits.
  • Added 2 new features to the Results Box field
    • Ability to put in any fields you wish, meaning you do not have to set this option in the source bloc that the field is getting the data from.
    • Ability to set colours in the results based on values.
  • Created a new Blocworx Permission called “Admin: Full Administration Only” where the user has unlimited access except for the ability to do building/development.
  • Added a new feature where an asterisks is shown if a field has the “Cannot be Empty” rule applied to it. This is better UX and imitates normal forms that have a * Required field.
  • Improved the Date Difference field so that different formats can be compared to each other.
  • Improved our Template Exporter to support the Checkboxes from Bloc field.
  • Created a Bluetooth field (currently a Beta version).
  • Created the first version of our Blocworx Gateway Field.
  • Added Rule/Action calling to the Cross Bloc Data Manipulator Field.

Release Notes


  • Fixed intermittent issue with the default skin appearing as the bright one.
  • Made improvements on the grid/layout of Blocworx to handle more unexpected situations with data and field numbers.
  • Added the ability to hide the second Blocworx logo along with the release number (for UI and cleaner output).
  • Added the ability to change the footer message in any Mail Alert output including in Reports.
  • Made huge improvements to our Look Up Data page allowing the user to isolate searches by single fields.
  • Created a new Barcode Generator Field.
  • Made some minor background improvements so our automated tests could run smoother.