Runtime Settings

📄️ Feature Overview

InRule's Runtime Overrides let you point the Decision Platform between develop, test, and production environments securely.

Create a Runtime Override from the SaaS Portal's Manage screen by setting its Type, Property, Name, and Value.

Edit, save, discard, or delete a Runtime Override from the SaaS Portal's Manage screen using its pencil, checkmark, and trash icons.

Set the catalog credentials the Rule Execution Service uses in the SaaS Portal, created via the Web Catalog Manager.

InRule's Runtime Overrides API is secured with primary and secondary API keys and is OAS 3.0 compliant.

InRule's API requests the latest overrides from InRule's engine, which interprets them and returns the resulting actions to the application.

Copy the Primary API Key from the portal's Configurations > Execution > Manage screen to authorize Runtime Overrides API calls.

Try out and test Runtime Overrides API methods directly on the API page using Try it out and Execute.

Integrate the Runtime Override API into an Azure Pipeline using curl and an API key copied from Configurations > Execution > Manage.

A sample Azure Pipeline script that lists, adds, and re-fetches Runtime Overrides via the API.