One of the great things about InRule is that there are numerous spots within the product where you can extend native functionalities to be able to easily support integrating with new things that we haven’t added into the core product (yet). One of those areas is...
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...
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...
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...
In the first part of this two-part series, we created a Rule App that calls out to an irServer REST Rule Execution Service (RES) – if you haven’t already, I’d highly recommend reading through that first. In this part, we’re going to briefly touch on how to configure...
Warning: in the InRule Blog, we have a wide variety of posts – some are targeted towards business users, and others are targeted towards the more technical side of our customer base. This post is the first in a two-part series about interacting with REST...
In a previous post, we looked at the fantastic integration options that are available out-of-the-box with our Salesforce integration. While the functionality that integration provides will be sufficient for the majority of InRule customers, there are always edge cases...
It’s been over three years since we introduced InRule for Salesforce, and our Salesforce integration is now stronger than ever. If you want a deep dive into the integration, you’re in luck – we just released a webinar that goes into all the juicy details. Want to dive...
Introducing the irAuthor Merge Extension What is a merge tool? While InRule is designed to empower business users to author their own rules, there will inevitably be folks from the IT side of the organization that interact with business rules at some point – be it for...
Welcome back! For those of you just joining us, this is part two of a pair of blog posts discussing CI/CD with rule apps – you can find the previous post here. Part Two: irCatalog Check-In Triggered, Catalog-Sourced Rule App, Promoting Pipeline Scenario: For this...
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.