Configuration Overview

  • Updated

The configuration application of the Portal is an absolutely crucial and comprehensive tool that enables users to configure all of their InRule environments. Its vast capabilities make it an indispensable asset for achieving optimal performance and ensuring seamless operation across all relevant systems. With this powerful tool at your disposal, you can confidently customize and fine-tune your InRule environment to meet your business needs and stay ahead of the competition.

Configuration Overview.png

Using the Configuration page

With the exception of Runtime Overrides, the content of the sections is editable, but you are unable to create new configurations on the page. 


Hover over the configuration you would like to edit and the below options will appear.  Click on the edit configuration icon to edit the configuration.


You can click on the copy icon wherever you see it to copy the information next to it.  


Some configurations have a toggle so you can enable or disable them. You must click on the Edit button in order to be able to move the toggle. 


Show / Hide Values

  • Clicking on the Show Values button shows the values of the configuration in that section.

  • Clicking on the Hide Values button hides the values of the configuration in that section. 

  • Clicking on the Toggle Visibility icon will show or hide the values in that row. 


Save / Cancel 

Once you have opened a configuration for editing, you have the option to Save or Cancel the edits.

Save : Cancel.png

Dynamics 365 Runtime Settings

You can access and update the Dynamics configuration settings in this section. To read more, see the Dynamics documentation here, InRule® for Microsoft Dynamics 365 Deployment Guide (5.5 MB).

Execution Runtime Overrides

Here you can add, delete, and edit the configuration of a Runtime Override. See more documentation here in the Execution Runtime Overrides section.

Execution Server Settings

Execution Server Settings.png

Catalog Connection

An optimal way to provide these credentials is by entering them here, on the Configuration page. 

1. User Name and Password: The User Name and Password are created in the Web Catalog Manager when adding or editing a user. Once credentials are set, it is added here to expose it to the Rule Execution Service. It is essential that the information here matches the information in the catalog.

2. Allow Per Request Catalog Credentials: Turning on the toggle will allow the catalog credentials to be passed to the Execution Service through a REST request. By default, the Allow Per Request Catalog Credentials toggle is turned off. It is recommended to keep this toggle off for security reasons.

Catalog Rule Application

3. Enable Background Compilation

The setting is a Boolean. If true, the polling operation is performed on the Catalog to see if a newer version of the rule application version is available. If a new version of the rule application exists, the download, compilation, and caching of the new version will be performed on a background thread. The default is false.

4. Pre-compile All Rule Apps

When set to True, Decision Services will perform an automatic compilation of all rule applications contained within the Catalog upon startup and before indicating that it is ready to receive execution requests.  The purpose of this is to allow new scaled-out instances of the Execution Service to have gone through a functional “cold start” process prior to requests being routed to it, preventing the initial requests going to a new instance of the execution service from taking a longer duration due to the rule application compilation process that is required for new rule applications within an execution service instance.  This setting does not apply to the legacy Rule Execution Service, Dynamics, or Salesforce execution services.

5. Rule Application Label

When this configuration setting has a non-empty value, Rule Executions will be performed using the specific Revision of the requested Rule Application to which this setting’s label has been applied within the Catalog instance. This value must match the Label in the Catalog, and that Label must be applied to a revision of the requested Rule Application for the execution to be successfully completed.

Rule Engine

6. Compiled Application Cache Depth

The first time a Rule Application is requested, it must be compiled so the rules engine can execute the rules.  Once a Rule Application is compiled, it is stored in an AppDomain cache for subsequent executions of the application. If this number is exceeded, the oldest compiled rule application is removed from the cache in favor of the newest compiled application. The default is 25. 

General Settings


Detailed application event information from InRule can be logged to the Windows Application Event Log by configuring the log settings. 
At this point, only the level of logging can be modified in the configuration application. Adding this setting will override all level settings for loggers.

Group-level settings can be one of the following: Debug, Info, Warn, Error, Fatal.

Salesforce Runtime Settings

Salesforce settings are updated in this section. You can access the Salesforce documentation here, InRule® for Salesforce Deployment Guide (3.5 MB).

Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.