Roadmap 🚲 🗺️
Public roadmap
Last updated
Was this helpful?
Current Version
Public roadmap
Last updated
Was this helpful?
The roadmap serves as a general plan of the future development. It includes new features as well as significant improvements of the software or services
Some of the features don't have to meet the dates set. They can be released sooner or later. We always focus on the most important things and customer needs.
We will improve upon the workflow performance to increase the effectivity of the calculation for bulk payloads with large numbers of inputs. This will be achieved by improving workflow bulk solve logic and adding a couple of new features, like the ability to call business rules with bulk input and the so-called parallel foreach, which allows to loop over arrays and run the loop branches in parallel.
Some of our customers need to make extensive calculations over large data sets which would take minutes and hours instead of seconds. Thanks to this ground-breaking feature, DecisionRules will support this use-case out of the box.
We are working on the ability to connect DecisionRules directly with your database. With this feature, you will be able to make custom queries, reading and writing data during your decision-making process. This will greatly help our clients seeking the ability to perform computations over large data sets.
We are constantly trying to make our app more user-friendly and easy to use. Driven by this effort, we would like to present an updated app layout with better and more logical structure and improved user experience.
We will prepare an update of the DecisionRules server with optimized queries to Redis and support Redis cluster mode. This will improve the performance of the solver for high-traffic applications and enable to use computation resources more effectively.
We will release DecisionRules version 1.19.0+ for on-premise/private cloud, therefore bringing the new powerful features currently available in the public cloud to our on-premise customers. The most important features include workflow, calculation columns and UX improvements in decision tables and a significant performance boost.
We are dedicated to continuously improving the UX/UI of the application to make it more efficient and smooth for the end users. This time we preparing a couple of more significant changes, like an update of the login/registration forms, the layout, and some of the inner components of the app.
We will implement an offline licensing mechanism to make DecisionRules available to on-premise/private cloud customers who cannot use the standard online license for reasons specific to their environment.
We will release a brand new rule type – the workflow – which will allow you to easily build complex flows of rules with support for branching, external API calls, in-rule scripting, possibility to call other rules with different strategies, data transformations, and much more.
We will enrich the decision table with calculation columns so that you can perform custom calculations anywhere in the table, even in the conditions section.
We are committed to provide some important improvements of the decision table UI/UX to make to work with decision table more smooth and effortless. We will improve the behavior of individual cell and make its editing easier, and add ways for easier value transfer across cells.
We will release an Excel add-in that will allow Excel users to call DecisionRules and solve rule with data from a chosen Excel sheet. Upon one click, the add-in will call DecisionRules with the specified input data, and create a new sheet with the outputs.
We will build a Power BI connector which will simplify connecting Power BI to our Audit API. You will be able to simply choose the connector, enter the BI Key and the filter, and load the audit logs in question without writing any custom code.
We will release a brand new rule type – the workflow – which will allow you to easily build complex flows of rules with support for branching, external API calls, in-rule scripting, possibility to call other rules with different strategies, data transformations, and much more.
We will enrich the decision table with calculation columns so that you can perform custom calculations anywhere in the table, even in the conditions section.
We are committed to provide some important improvements of the decision table UI/UX to make to work with decision table more smooth and effortless. We will improve the behavior of individual cell and make its editing easier, and add ways for easier value transfer across cells.
We will allow for centralized management of spaces, accounts, and permissions by an organization admin. The admin will be able to invite new members to the organization and perform actions like listing or removing the member accounts. Likewise, the admin will be able to manage the organization spaces and control the permissions of the members for the individual spaces.
We will provide new endpoints for the Management API dedicated to managing folders. You will be able to perform all the basic CRUD operations over folders, and manage rules in the folder structure via the new API endpoints. These will naturally expand the Management API capabilities to folders and enable you to perform complex rule migrations.
We are constantly trying to improve our accessibility for the international audience. After English and Spanish, we will provide a translation of the whole app to Portuguese. Fique atento!
We will open a whole new platform for our business users to easily and effortlessly learn DecisionRules through a series of simple tutorials rich in screenshots and gifs.
We will enable to authenticate your calls to the Solver API via OAUTH as a more secure alternative to API Keys.
We will introduce a new type of rule which will allow the user to set up a collection of constant values to be used in other rules within the space. These values will be easily editable and accessible. You will be able to use dictionary for storing configurations or as a simple lookup table.
We will add the functionality of comparing two decision trees. The user will be able to see the tree differences, merge the content from the secondary tree or edit the primary tree arbitrarily. This feature will greatly simplify handling conflicts between distinct versions of decision trees.
Lately, our customers have been asking us about a way to lock an important / production rule to protect it from change or deletion. We will implement this feature for you. There will be special permissions needed for managing the lock, so you can easily prevent some users from editing the locked rules.
You can have the application show the logo of your company instead of the default DecisionRules logo. This is the first step of our custom branding, which will allow you to choose the logo, colors and types matching your company's visual identity. Available only for on-premise or private (managed) cloud solutions.
We will update our most used SDK to include the newest API endpoints, be aligned with the documentation and covered by automatic unit tests.
We will add the functionality of comparing two decision tables. The user will be able to see the table differences, merge the content from the secondary table or edit the primary table arbitrarily. This feature will greatly simplify handling conflicts between distinct versions of decision tables.
We will add the functionality of comparing two decision trees. The user will be able to see the tree differences, merge the content from the secondary tree or edit the primary tree arbitrarily. This feature will greatly simplify handling conflicts between distinct versions of decision trees.
We will let you know who is currently viewing the same rule as you. This will help you organize your teamwork and prevent problems stemming from mutual interference of rule editors.
We will allow users to view and search dependencies of all types of rules. Thanks to this, you will be able to quickly and easily see all the rules that enter a given process. The dependency search will also help when performing group operations over rules, e.g. to check whether a given operation does not break your process. The functionality will be available both in the app and via Management API.
Have you ever wondered why you cannot export multiple rules at once? Well, we will bring this capability soon. You will be able to export the whole folder with all its rules to a single file and import it back. This way, you will be able to simply create backup files or share rules between spaces or even environments with one click.
We launched 24/7 service line support and we are now able to respond to critical issues in the matter of hours, day and night. This is mainly important for our larger customers who need robust and fast support all around the world.
In addition to our global cloud, we launched three individual regional clouds for Europe, the USA, and Australia. Each regional cloud has its own environment and database so it can be guaranteed that all data are stored only in the respective region. Thanks to this, you may now use DecisionRules as a service while still keeping aligned with your data residency policy.
We added the functionality of comparing two scripting rules. It is now possible to view the differences between two scripting rules and edit the primary scripting rule, reflecting the differences in the way you like. This feature will greatly simplify handling conflicts between distinct versions of scripting rules. Similar rule comparison features are planned for decision tables and decision trees.
We added support for languages and provided translations into Czech and Spanish.
We will add support for using rule alias instead of rule ID within Management API. Thanks to this, you will be able to use rule aliases for most operations concerning rules. Together with this, we will make a general revision of security and effectiveness within the business logic treating rules and spaces.
We will bring better organization of rules using folders for larger spaces. We would like to enable user and automated transfer of folders between spaces or individual physically separated environments.
This feature will make it possible to create parametrizable JSON objects and fundamentally expand the possibilities of decision tables and decision trees when using integration functions or changing output data in JSON format.
We would like to make decision tree nodes collapsible to improve the overall experience when editing decision trees.
Migration of rules is a big topic for us lately. So far, one can only manage single rules via Management API. We therefore want to provide a free customizable migration tool for anyone to use.
We will bring better organization of rules using folders for larger spaces. We would like to enable user and automated transfer of folders between spaces or individual physically separated environments.
We would like to enable easier transfer of multiple linked rules between spaces and environments. You will be able to prepare and test the entire rules release, which you can then easily transfer to another space or environment.
Now is a good time to switch to the new major LTS versions of the AWS platform that power our public cloud.
We will simplify the possibility of returning the default output in the event that no row in the decision table is fulfilled.
We would like to enable our customers to pull data from external sources in a rule using the REST API and do a simple data transformation on it.
We would like to allow our customers to nest RuleFlows within other RuleFlows.
With the growing number of users, we have received a large number of requests to improve RuleFlow. We would like to clarify the requirements and then implement some of them. You definitely have something to look forward to.
We come across many interesting use-cases in which you use DecisionRules. We would like to outline and describe the main trends in individual sectors in such a way that it is clear how to use DecisionRules and where it has the greatest added value. We believe that this will save you some time in implementation projects.
Our advanced features are often used in Decision Tables and Decision Trees. We're taking our feature and expression editing to a whole new level. We'll let you edit rules using VS Code on the web.
We would like to enable our customers to pull data from external sources in a rule using the REST API and do a simple data transformation on it.
Simple and fast work is written in our DNA. Many customers write to us why we do not yet have a video tutorial to show how easy it is to work with DecisionRules. ... Working on it.
The new structure of decision trees will make your rule to edit process easier and faster because of a tree structure.
We want non-technical users to feel good with us. That's why we're working on how to easily enter input data into rules and how to display them easily. The possibility of using the JSON format will of course be retained.
We are gradually expanding our platform to make it easier from an integration perspective. According to customer votes, this is also related to the possibility of calling external APIs from the scripting rule.
DecisionRules handles millions of rules per month. Related to this is the constant improvement of our monitoring so that we can better prevent problems before they occur.
We know that for many of you it is difficult to try DecisionRules in on-premise mode on your infrastructure. For new users who are about to try DecisionRules on AWS/Azure, we are trying to create a 1-click solution for installation from the Azure/AWS Marketplace.
Better Power BI integration for on-premise and cloud users
Each rule made by the user can be saved in the library. Those rules will be able within the space regarding permissions. It can be helpful for rules which are used more often, for example, client validation.
The new structure of decision trees will make your rule to edit process easier and faster because of a tree structure.
Ability to assign permissions to the user within the space. Permissions will be granular, so creating your own sets of permissions will be available.
Evaluate more rules simultaneously, for example sending 100 inputs, and the output will be for the same amount as input was.
General overview of decision tables and easier display of help for operators and functions.
Define variables in the rule settings, which you can then use indefinitely in the decision table
The variables are versioned together with the rule
Guide/how-to videos alongside our documentation.
Export/import rule flow, sharing in between the spaces, graphical changes, connecting rule flows through more spaces,...
Asynchronous Kafka Messages Support for Cloud and On Premise Version (Apache Kafka Solver API)
Faster resolution of rules across the globe
Increased resistance to outages
This feature will provide an ability to put rule after rule to make a "chain," which will be executed as one rule made of more.
If you don't want to use our web app, you can download and configure the Docker container in your environment.
Filter, order by, and search functions over decision tables in the application to a better overview and edit the tables.
Management API allows making operation with spaces/rules even without a need of using UI of DecisionRules, such as retrieve the rule lists with the appropriate information.
Editing, adding or deleting more rows in the table at the same time.
Our customers requested the possibility of specifying which conditions columns will be activated when calling a decision table via the Rule Solver API. It is now possible to include or exclude columns, making the solve of decision table even more flexible.
