With the new DocumentBuilder, we have not only built mandatory requirements but stacked a cherry on top. As a result, we offer a wide range of functions and a high level of flexibility for document templates. Thanks to this extended customisability, documents can now be set up according to marketplace-specific guidelines more easily and more design options are available in general. In addition, electronic invoice formats can be used – securely and GoBD-compliant. The cherry on top: We have created a user-friendly interface that enables easy setup and will save you a lot of time during setup of new templates.

As you will have noticed, we postponed the first EOL dates. During this phase we continued working on the DocumentBuilder but one of the main reasons was also to give you more time to set up new templates and switch to DocumentBuilder. We are now back on track and have not only announced the EOM for the old document templates but also the new EOL dates. With these, we again want to give you enough time to familiarise yourself with DocumentBuilder and to take all the necessary steps for the switch.

While you are preparing the switch to DocumentBuilder, we are working on a few improvements. Here, we are giving you an overview over the bigger features we planned for the rest of 2024.

Refactoring of variables

This is a back end improvement which means you will not see a difference in the user interface but will benefit from better performance. We offer you close to 700 variables in the DocumentBuilder and the more you use in a template, the more data needs to be handled. We implemented a new logic for the variables and moved them group by group. This has already been completed by us in the last months.

Tooltips for variables

Up to now, we had not been able to offer explanations or tooltips for variables directly in the user interface. We had to rely on meaningful and precise variable names but soon saw the limits of these. Therefore, we have been working on making tooltips for variables possible in the DocumentBuilder. The basic functionality is already released and we will now continue with polishing this but most importantly, of course, with adding more and more variable explanations.

Asynchronous data collector

A benefit of DocumentBuilder and the new logic for document generation is that we are now able to monitor much more closely what is going on. This includes performance, an important topic for you and for us. This is also where asynchronous processes come in. A lot of the technological basis is already working asynchronously. Simply put this means that the execution times of different steps may differ. What it also means is that we are much more flexible because of higher scalability – leading back to better performance.

Therefore, we plan to change the data collector of the DocumentBuilder to an asynchronous data collector, thereby reducing the time of document generation once again. As with the refactoring of variables, this is also a back end improvement. This is one of the next features, we have not started working on it yet.

Widget restriction

We see how much you benefit from the restrictions in the text widget and therefore want to extend these to settings for the different widgets so that you can define the conditions when a widget is displayed on a document. Thus, you will be even more flexible in the setup of your document templates because one template can more easily be used for different use cases.

So far this is a planned topic only. When we start with this, the first step will be analyses and groomings.

Questions, interest in and feedback for DocumentBuilder are always welcome – please feel free to contact us about this any time. We will publish regular roadmap updates.