InRule Decisioning Version 5.7.3 Release Notes
| Type | Case ID | Summary | Description |
|---|---|---|---|
| Story | CAD-270 | Add configuration for Certificate Validation | A new setting has been added to allow certificate validation to be toggled for development purposes. See documentation on details for how to configure this setting. |
| Story | CAD-274 | RES REST request accepts catalog credentials | A new setting has been added to Rule Execution Service config file called "allowPerRequestCatalogCredentials" which specifies if catalog credentials will be accepted on Rule Execution Service REST requests. By default, this will be set to false. Therefore, catalog credentials will need to be added to the config to allow run time applications to continue running uninterrupted. It is also possible to set "allowPerRequestCatalogCredentials" to true to keep functionality same as before, but it is not recommended. |
| Story | CAD-271 | Web Catalog Manager expiration | A new setting has been added Web Catalog Manager config file to set the expiration of the authorization cookie. By default, it is set to 8 hours. After 8 hours of inactivity (or the length of time AuthCookieExpire is set to), the authorization cookie will expire and require the user to login again. This change only affects database authentication configurations. When using centralized authentication, expiration is handled by the OIDC provider. |
| Story | CAD-258 | Add ability to hide Defs in irAuthor | Added the ability for developers to hide endpoints, schemas, rules/actions and data operations from the irAuthor navigation pane. |
| Story | CAD-327 | Allow overriding the headers and body on a REST operation | Added the ability to override Headers, Body and UriTemplate on a REST operation. A new sample has been added to github as well as documentation updated. |
| Story | CAD-261 | Error when adding an explicit rule set with parameters to a rule application | Adding an explicit rule set with parameters to a rule application that has an existing BL execute rule set command will no longer produce an error. |
| Story | CAD-382 | Add ExecutionLog interface similar to metrics | ExecutionLog interface has been added to irSDK runtime and can be used by a consumer to access the RuleExecutionLog post rule execution. This can be configured via irSDK RuleSession.Settings or via the config file. |
| Story | CAD-413 | Investigate user's nav pane order not being respected | -Fixed a bug where the user's preferred navigation pane order was not being preserved when irAuthor was closed and then opened again.- |
| Defect | CAD-315 | Public DecisionTable functionality in irSDK will always throw Exception if called | Fixed issue with Remove method for ConditionValueDefCollection and ActionValueDefCollection in irSDK. |
| Story | CAD-309 | Set the irVerify Option for "Enable test data reset" to ON as a default | irVerify Option for "Enable test data reset" is now turned on by default. |
| Story | CAD-386 | Allow on-prem customers to use their own Okta account | On-prem customers may now use their own Okta/Auth0 account to login. |
| Story | CAD-249 | Issue with running difference report | Resolved an issue that resulted in error when running a difference report on a rule application that has decision table changes. |
| Story | CAD-378 | irAuthor: When navigating, the nav pane doesn't always scroll properly | Resolved an issue where navigation pane in irAuthor intermittently didn't navigate to the correct item. |
| Story | CAD-352 | ApplyRules uses the wrong timer | Resolved an issue with the total execution time in the Rule Execution Performance report. |
| Story | CAD-273 | Increased security | Security improvements were made. |
| Story | CAD-380 | irVerify: Apply/Add appears disabled until hover | Tweaked color scheme in irVerify so that enabled items do no look disabled. |
| Story | CAD-379 | irAuthor: When navigating, nave pane doesn't highlight the item in the right color | Tweaked color scheme in the irAuthor navigation pane. |
| Defect | CAD-314 | Enable icon in irVerify Home tab is confusing | Updated Enable icon in Rule Tracing section of irVerify ribbon. |
| Defect | CAD-377 | Web Catalog Manager: outdated support link | Updated old support links in Web Catalog Manager to direct user to email InRule Support. |
| Story | CAD-257 | Re-order the Nav Pane in irAuthor | Updated the default order of the navigation pane in irAuthor. |
| Story | DYN-469 | InRule for Microsoft Dynamics 365 - Remove support for custom s2s connection configuration | The legacy S2S connection settings are now no longer supported by the Rule Execution Service. S2S configuration should transition to using an OAuth connection string. For more information on this change, refer to the InRule for Dynamics Deployment Guide. |
| Story | DYN-568 | InRule for Microsoft Dynamics 365 - irX Test button - provide drop-down menu for entity and decision contexts | Expanded the functionality of the Test button in the Dynamics tab to include the dropdown feature present on the irVerify button. Clicking on the Test button in the Dynamics tab will now allow you to quickly select the most recently used entity or decision contexts. |
| Story | DYN-603 | InRule for Microsoft Dynamics 365 - Create Dynamics 'Rule Executor' role for user rule execution privileges | The InRule Rule Executor role has been added to the InRule Dynamics Solution. This role will be automatically created upon deployment of the solution, and allows for easy assignment of all the minimum required permissions needed to leverage the Run Rules button within the Dynamics UI. Any non-admin users that will need to run rules through the UI should be added to this role. |
| Story | DYN-616 | InRule for Microsoft Dynamics 365 - Update irX and rule execution service to Xrm 9.1.0.79 | InRule for Dynamics 365 has been upgraded to use Dynamics SDK v9.1.0.79. |
| Story | DYN-623 | InRule for Microsoft Dynamics 365 - Show success or error information on Admin Consent redirect page | Enhanced feedback from the admin consent page within the InRule SaaS portal to provide users with a better sense of when consent has successfully been granted or if there has been an error. |
| Story | DYN-626 | InRule for Microsoft Dynamics 365 - Add query filter parameter to LoadMappedChildCollection RuleHelper method | Add a query filter parameter to the LoadMappedChildCollection RuleHelper method. This allows for filtering down especially large collections so they do not need to be loaded in their entirety. |
| Story | DYN-630 | InRule for Microsoft Dynamics 365 - Manage error handling for Run Rules button in scenarios where a user doesn't have permissions | Updated error handling to inform the user more informatively when they don't have appropriate permissions to use the Run Rules button. |
| Story | DYN-632 | InRule for Microsoft Dynamics 365 - Create Azure Marketplace listing for InRule for Dynamics 365 | The InRule for Dynamics 365 Execution Service (with optional Catalog Service) is now available on the Azure Marketplace. This provides a straightforward, UI-driven approach to deploying the Dynamics Rule Execution Service. This approach requires far less manual Azure management steps. |
| Story | DYN-641 | InRule for Microsoft Dynamics 365 - Validate compatibility with 2021 Release Wave 2 | - |
| Story | DYN-650 | InRule for Microsoft Dynamics 365 - Add 'Clear Cache' button to Rule Configuration page | A "Clear Cache" button has been added to the Rule Configuration page. This allows users to manually clear the AppDomain cache for all RuleHelper queries configured for caching in the Rule Execution Service. |
| Story | DYN-673 | InRule for Microsoft Dynamics 365 - Expose catalog label as parameter in ARM Template | ruleAppLabel has been added as a parameter to our ARM templates, allowing customers to specify a default catalog label to be used by the rule execution service. |
| Defect | DYN-538 | InRule for Microsoft Dynamics 365 - Money fields show up twice on irX schema selector, 2nd instance shown as (base) | Added a toggle to irX to allow for displaying/hiding Money (Base) Dynamics fields. By default, these fields will be hidden. |
| Defect | DYN-604 | InRule for Microsoft Dynamics 365 - Created By Lookup Not Mapping in irAuthor | Fixed a bug that was causing the "Created By" lookup field to not be properly mapped by irAuthor. |
| Defect | DYN-644 | InRule for Microsoft Dynamics 365 - 401 error when using test connection with a S2S (Client Secret) connection type | Resolved a bug that was causing the Test Connection button to fail when using an S2S connection. |
| Defect | DYN-662 | InRule for Microsoft Dynamics 365 - 400 Bad Request when root entity contains large text field | Fixed a bug that caused the Rule Execution Service to return a '400: Bad Request' when the root entity being operated on contained a large text field. |
| Story | DYN-681 | InRule for Microsoft Dynamics 365 - SaaS Portal config dynamics authentication type - change Office365 to OAuth and other content | The Dynamics connection string management via the portal has had the selections for authentication type updated to reflect the deprecation of Office 365 connection strings. |
| Story | SFC-70 | InRule for Salesforce - Allow for 1:N querying in rule helper query filter expression | Support for 1:N querying in the Rule Helper query filter expresion has been added for Salesforce. This allows for 1:N queries, multiple 1:N relationships in a query (for example, Account: "Contacts.FirstName == 'John' and Cases.CaseStatus == 'Open'"), and N:1 from 1:N queries (for example, Account: "Cases.Owner.FirstName == 'John'"). |
| Story | SFC-219 | InRule for Salesforce - Create Azure Marketplace listing for Salesforce | The InRule for Salesforce Rule Execution Service (with optional Catalog Service) is now available on the Azure Marketplace. This provides a straightforward, UI-driven approach to deploying the Salesforce Rule Execution Service in Azure and requires far fewer Azure management steps than deploying via ARM template. ARM Templates are still available to support advanced scenarios and DevOps automation. |
| Story | SFC-226 | InRule for Salesforce - Add filter parameter to LoadMappedChildCollection RuleHelper method | Add a query filter parameter to the LoadMappedChildCollection RuleHelper method. This allows for filtering down especially large collections so they do not need to be loaded in their entirety. |
| Story | SFC-228 | InRule for Salesforce - Provide an on-prem rule execution service installer MSI | An installer MSI is now available for the on-prem Salesforce Rule Execution Service to help streamline the installation process. |
| Story | SFC-229 | InRule for Salesforce - Expose DecisionClient over REST | The Salesforce DecisionClient Apex class, which orchestrates rule execution in Salesforce, now has an exposed REST endpoint in addition to its existing SOAP endpoint. This endpoint accepts a JSON string that contains the serialized rule execution parameters, and returns a string containing the serialized rule response. |
| Story | SFC-236 | InRule for Salesforce - Add 'Clear AppDomain Cache' button | A "Clear Cache" button has been added to the InRule Configuration page, under the Custom Settings header. This allows users to manually clear the AppDomain cache for all RuleHelper queries configured for caching in the Rule Execution Service. |
| Story | SFC-238 | InRule for Salesforce - Validate Winter '22 Release | - |
| Story | SFC-239 | InRule for Salesforce - Update Salesforce api version to v53.0 | InRule for Salesforce compatibility with the Winter 2022 release has been verified. API versions in the InRule Salesforce package, execution service, and irX have been updated to v53.0. |
| Story | SFC-244 | InRule for Salesforce - Provide 64-bit deployment options for App Service deployment | The Salesforce Rule Execution Service now supports 64-bit deployment. Previously, only 32-bit deployments were supported to ensure compatibility with all tiers of Azure App Services. This is not directly configurable, but is rather determined by what tier of App Service plan is deployed, with tiers "F1" and "D1" continuing to deploy as 32-bit, and all others deploying as 64-bit. |
| Defect | SFC-220 | InRule for Salesforce - DateTime and Date fields incorrectly showing as entity changes in RuleResponse | Fixed a bug that was causing Date and DateTime fields to be incorrectly flagged as entity changes in the rule response. |
| Defect | SFC-222 | InRule for Salesforce - User parameters need to be set to 'Not Required' in the SaaS ARM template parameters file. | |
| Defect | SFC-224 | InRule for Salesforce - Post Install Script Failing On Upgrade | Fixed a bug that was causing the Salesforce post-install script to fail during upgrade scenarios. |
| Defect | SFC-247 | InRule for Salesforce - Clear collection/Remove member throws Apex timeout error | Fixed a bug in collection loading logic that was causing removing collection members as a part of rule execution to throw an error. |
| Story | SFC-248 | InRule for Salesforce - InRule Lightning control button improvements | Enhanced the Run Rules Lightning component to make descriptions of the rule set associated with the button more clear. As before, when you enter multiple rule set names in the Lightning control, each Run Rules button will be labeled with their Rule Set name. Now however, when only defining one rule set, the button will still be labeled with that rule set name. If no rule set is defined, it will be labeled generically "Run Rules" and will run the Default rules for the given entity. Additionally, the Lightning control now supports spaces in rule set names for readability purposes. Adding spaces to the control will not impact its ability to map to a rule set. |
| Defect | SFC-249 | InRule for Salesforce - SaaS Portal Salesforce Connection Test Enhancement | The Test Salesforce Connection button in the InRule SaaS Portal has been enhanced to eliminate false positive scenarios and provide more informative errors to the user when connectivity fails. |