Roadmap

Our platform and technology is constantly evolving

We know our technology inside out and love to share it with business engineers, architects and developers. Take a look at our roadmap and see what we're working towards now. Or check out our Research page and get an idea of our research projects.

Each item on our roadmap is linked to one of the categories within our platform, namely Engage, Work, Decide, Learn and Adapt. You can see on this image what each category enables. And so we are continuously enriching that, as you can see in our roadmap.

platform

Q4 - 2024

Nullability in REST communication

Adapt Completed

Release: 17.7

Improved data integrity through control over whether 'null' values sent or received by Blueriq APIs/applications are accepted.

Q4 - 2024

OpenAPI import in Encore

Adapt Completed

Release: 17.6

Faster innovation through automated modeling steps for invoking and creating JSON-based REST services.

Back to roadmap

OpenAPI import in Encore

Adapt Completed

Faster innovation through automated modeling steps for invoking and creating JSON-based REST services.

  • Category: Adapt
  • Release: 17.6
  • Quarter: Q4 - 2024
Tijmen Daatselaar
Tijmen Daatselaar
Product Owner

Why

The design-time import of an XSD or WSDL file to create or call a SOAP service has been available for years in the Blueriq platform. This functionality has proven itself time and again: it saves time, enables faster innovation at lower costs, and makes the business engineer's work easier and more enjoyable.

What

Despite the growing popularity of JSON-based services, calling and creating them is still a manual process. To minimize this cumbersome, time-consuming, and error-prone task, we are implementing an import feature for calling and creating JSON-based REST services.

Back to roadmap

Nullability in REST communication

Adapt Completed

Improved data integrity through control over whether 'null' values sent or received by Blueriq APIs/applications are accepted.

  • Category: Adapt
  • Release: 17.7
  • Quarter: Q4 - 2024
Tijmen Daatselaar
Tijmen Daatselaar
Product Owner

Why

Although the value 'null' is not recognized in the Blueriq profile, we still encounter it through REST messages. Currently, an incoming 'null' in Blueriq is always accepted and interpreted as a value that has been intentionally left empty: user set unknown. The inability to reject a 'null' value is currently not easily possible, and we want to change that to gain more control over the data that enters the Blueriq profile.

What

We will make it possible to specify for each field (in a domain schema) whether 'null' is allowed. This choice will be adopted during the OpenAPI import and communicated in the OpenAPI feed to the outside world as well.

Blueriq Community

All the ins and outs of the Blueriq Platform?

Documentation, how-to's and the ability to ask questions, you'll find it all on the Blueriq Community. The Community is for anyone working with or interacting with Blueriq and is openly available.

To the Blueriq Community
our-approach_1

Want to know more?

Do you have questions about new developments or are you curious about all the possibilities of the Blueriq platform?
If so, please contact Yuri.

Contact
Yuri
Versluis
Strategic product manager