If you’re like many InRule® customers, your AD&D and DevOps teams are investigating or have already adopted a continuous integration, continuous delivery (CI/CD) pipeline approach. Moving to CI/CD has several benefits: Code changes are smaller and easier to manage, resulting in fewer unintended consequences. With testing done as soon as code is integrated, developers can […]

Like many InRule users, my background is in software development. As a result, I often find myself taking whatever means I can to bypass low-code tools: When I need to make changes to a WordPress website, I inevitably become annoyed at the rich text editor and end up making changes directly to the HTML When […]

In my last post, I discussed ways to programmatically modify Rule Applications in code to handle different configurations and data requirements in different environments. While that method is certainly useful, it takes significantly more effort than is necessary to fit the needs of the vast majority of InRule customers. Today, we’re going to look at […]

Managing the reference data required by a decision is a common challenge for most rule applications. And depending upon your requirements, you have several options for storing that data, such as SQL Endpoints, cloud-based databases, and external service options. But there are a few powerful use cases for storing your reference data in inline tables, […]

Warning: As with the previous posts about Continuous Integration/Continuous Deployment, this post is intended for a technical/developer audience. Background A while back, I started a series about CI/CD with a pair of blog posts that walk through examples of ways to include InRule in your CI/CD pipeline. Among other things, I covered how to retrieve […]