Feature Overview

Pointing the InRule Decision Platform from One Environment to Another is Simple

Keeping separate environments for develop, test and live production is made easy with InRule's runtime overrides. This documentation covers how to quickly and securely point the InRule platform using three different configuration methods for configuring overrides.

Available methods to configure runtime overrides:

• irServer Rule Execution Service
• SaaS portal
• An API

irServer Rule Execution Service

Available for on-premises and private cloud deployments.

Description	Table
Inline Table	Data
Inline Value List	Data
Inline XML Document	Data
SQL Query	Data
.NET Assembly Function Library	Data
Database Connection	Endpoint
REST Service	Endpoint
Send Mail Server	Endpoint
Web Services	Endpoint
Workflow	Endpoint
XML Document Path	Endpoint
REST Operation	Data

Overrides via the SaaS Portal

Available features for InRule hosted SaaS deployments.

Description	Table
Inline Table	Data
Inline Value List	Data
Inline XML Document	Data
SQL Query	Data
Database Connection	Endpoint
REST Service	Endpoint
Send Mail Server	Endpoint
Web Services	Endpoint
XML Document Path	Endpoint
REST Operation	Data

Overrides via API

This API capability provides a separate mechanism to control the endpoint configuration, allowing InRule to integrate seamlessly into the Azure DevOps release pipeline. When endpoints and configurations are altered, those changes can be applied to the configuration settings automatically for all components and applications in that environment.

Below is the list of runtime overrides that can be configured via an API and can be integrated into the CI/CD pipeline. Available for InRule hosted SaaS deployments.

Description	Table
Inline Table	Data
Inline Value List	Data
Inline XML Document	Data
SQL Query	Data
Database Connection	Endpoint
REST Service	Endpoint
Send Mail Server	Endpoint
Web Services	Endpoint
XML Document Path	Endpoint
REST Operation	Data