| Type | Case ID | Summary | Description |
| Outstanding Issue | SEAL-3881 | Cannot add an explicit rule set with parameters to a rule application if there is an existing Execute Rule Set action with parameters command written in the context of a Language Rule in the rule application. |
IMPORTANT: This is an unresolved issue and the fix is pending. The issue can be avoided in the meantime by using the Execute Ruleset command only in syntax. Users considering upgrading to this version should consider delaying their upgrade if their current implementation uses many execute ruleset actions with parameters or uses the execute ruleset action in a decision table. When a fix is available it will be posted in that version’s release notes. |
| FEATURE | DYN-405 | InRule for Microsoft Dynamics 365 - RuleHelper QueryCollection - deep referencing of collection name parameter | The RuleHelper now supports deep referencing of collections from the QueryCollection and LoadMappedChildCollection methods. This only works to load collections from lookup entities, not collections from other collections. |
| FEATURE | DYN-407 | InRule for Microsoft Dynamics 365 - Deprecate custom S2S authentication with built-in connection string support | The Dynamics SDK now natively supports connection string authentication with ClientSecret. This removes the need for the custom inrule:crm:s2s parameters. This functionality is now deprecated, and will be removed in a future release. Customers should switch to connection string authentication. Refer to the deployment guide for more information. |
| FEATURE | DYN-445 | InRule for Microsoft Dynamics 365 - Replace deprecated Xrm.Page references with ExecutionContext.getFormContext | Usage of deprecated Xrm.Page functionality has been replaced with ExecutionContext.getFormContext. This introduces a breaking change for the ExecuteRules JavaScript function, which now requires formContext as the first parameter. The deployment guide sample code has been updated to reflect this change. |
| FEATURE | DYN-447 | InRule for Microsoft Dynamics 365 - Remove solution support for Dynamics 8.2 and prior versions | The Rule Services Solution can no longer be installed in Dynamics 8.2 instances. Customers must use Dynamics 9.0 or higher |
| FEATURE | DYN-450 | InRule for Microsoft Dynamics 365 - Support Parameterized RuleSets prompting for primitive parameters from Run Rules button | Parameterized RuleSet dialogs have been added, allowing for passing in configurable parameters to rule execution at run time. |
| FEATURE | DYN-451 | InRule for Microsoft Dynamics 365 - Support for multiple rule app/rule set combinations in rule configuration | |
| FEATURE | DYN-462 | InRule for Microsoft Dynamics 365 - Use securestring for all sensitive ARM template parameters | The included ARM templates now use the ‘securestring’ data type to mask all sensitive string parameters. |
| FEATURE | DYN-466 | InRule for Microsoft Dynamics 365 - Improve error handling and documentation for request size limitation | Errors resulting from the Dynamics request-size limitation are now more descriptive. |
| FEATURE | DYN-468 | InRule for Microsoft Dynamics 365 - Enhance rule execution web job to support Decisions | The Rule Execution Service now supports Decisions in addition to traditional Rule Sets. The Decision must be defined with the root entity as the first parameter, and then be run in the context of that entity. |
| FEATURE | DYN-474 | InRule for Microsoft Dynamics 365 - Add support for Decisions to irVerify in irX for Dynamics 365 | Decisions can now be tested from irVerify. As with the execution service, Decisions must have one and only one Dynamics entity that is not a collection defined as an input. Additional inputs are permitted, but they must be primitive datatypes. |
| FEATURE | DYN-483 | InRule for Microsoft Dynamics 365 - ARM template options to designate existing Azure resources and other minor improvements | The Dynamics Rule Execution Service ARM template has had several parameter names updated to make their purpose more clear. |
| FEATURE | DYN-485 | InRule for Microsoft Dynamics 365 - Validate compatibility with 2020 Release Wave 2 | Tested all components of the InRule for Dynamics framework against a Dynamics 2020 Release Wave 2 environment |
| FEATURE | DYN-502 | InRule for Microsoft Dynamics 365 - Configuration for Rule Sets and Decisions in RuleConfiguration entity page | Rule configurations have been updated to use Rule Set configuration entities rather than a single rule set list field. The new Rule Set configuration allows for setting Display Names, Sort value, Description, and Parameters. This should not affect existing rule configurations; an upgrade to this new model will automatically occur when upgrading to v5.7.0. |
| FEATURE | DYN-510 | InRule for Microsoft Dynamics 365 - Allow for ordering of Rule Sets in Run Rules button | Ordering for Rule Set list associated with the Run Rules button is now configurable. |
| FEATURE | DYN-512 | InRule for Microsoft Dynamics 365 - Remove CreateEntity from Settings.InfoLevelLoggingTypes | In an effort to reduce clutter and event noise from Info leveling logging on the Rule Execution Service, CreateEntity events are no longer logged. |
| FEATURE | DYN-516 | InRule for Microsoft Dynamics 365 - Add support for passing in Rule App label to Rules Engine Action | The RulesEngineAction now supports passing in the "Label” parameter, which accepts a rule app label that overrides the rule app label defined on the rule execution service. If this parameter is not provided, the execution will default to using the configured rule app label as always." |
| FEATURE | DYN-517 | InRule for Microsoft Dynamics 365 - Add session ID to data loading log entries | The InRule session ID is now included as part of the data loading log entries to provide better correlation between them and other InRule log entries. |
| FEATURE | DYN-521 | InRule for Microsoft Dynamics 365 - Event Log improvements - Add Request Id, Connection Time, Total Service Execution Time | Improvements to the Rule Execution Service event log to provide new logs that display the total connection time to Dynamics and the total execution time of the entire request. Additionally, a Request ID has been stamped on every log related to an execute rules request, allowing for easier correlation across log entries. |
| FEATURE | DYN-527 | InRule for Microsoft Dynamics 365 - Add validation for Rule App, Rule Set and Rule Set param config fields | Added validation in Dynamics for fields that correlate to irAuthor name fields to ensure the same name convention validation that exists in irAuthor is applied in Dynamics. |
| FEATURE | DYN-528 | InRule for Microsoft Dynamics 365 - Auto-populate service endpoint ID when creating new rule config record | When creating a new rule configuration record in online Dynamics instances, the service endpoint ID will now automatically be set. |
| FEATURE | DYN-532 | InRule for Microsoft Dynamics 365 - Auto collapse Endpoint Configuration section when navigating to Rules Configuration Page | The Endpoint Configuration section will automatically collapse when navigating to the Rules Configuration Page if it is already configured. |
| FEATURE | DYN-540 | InRule for Microsoft Dynamics 365 - Add connection string support to ARM Template for AppInsights in Azure Govt cloud | The InRule ARM template now supports adding a connection string to use for AppInsights over using an Instrumentation Key for use in Government Cloud environments. |
| FEATURE | DYN-543 | InRule for Microsoft Dynamics 365 - Establish new Rule Configuration default values | New Rule Configurations in Dynamics will now have their configuration values set to default options to allow for quicker creation; these values can still be set normally afterward. |
| FEATURE | DYN-552 | InRule for Microsoft Dynamics 365 - irX - default Use Advanced Login to checked when adding New Dynamics Environment | When adding a new Dynamics environment to irX, the default authentication method is now set to Use Advanced Login. |
| FEATURE | SEAL-2823 | Ability to configure Info level logging in the SDK | Info level logging can now be enabled at a granular level from the SDK in addition to the .config file. This change also includes a 56% performance increase for logging. |
| FEATURE | SEAL-2872 | Remove the Publishing feature in irAuthor | The ability to publish a Decision to make it available for Decision Services will be moved to Author Studio, which will be available mid-year 2021. Decisions can be executed using irSDK, irVerify and our REST service. Documentation on how to use a Decision in this way is available here: * Using irSDK: [http://support.inrule.com/help/irSdkHelp50/executing_decisions.htm and http://support.inrule.com/help/irSdkHelp50/executing_decisions.htm] * Using irServer Rule Execution Service REST Endpoint: [http://support.inrule.com/help/irSdkHelp50/irserverruleexecutionservicehttp-executedecision.htm and http://support.inrule.com/help/irSdkHelp50/irserverruleexecutionservicehttp-executedecision.htm] * Using irServer Rule Execution Service SOAP endpoint: [http://support.inrule.com/help/irSdkHelp50/executing_a_decision_on_irserver.htm and http://support.inrule.com/help/irSdkHelp50/executing_a_decision_on_irserver.htm] * Using irVerify: [https://github.com/InRule/Samples/blob/master/Authoring%20Samples/Decisions/test-decision.md and https://github.com/InRule/Samples/blob/master/Authoring%20Samples/Decisions/test-decision.md|smart-link] |
| FEATURE | SEAL-2911 | Flagship: Add text to Web Catalog Manager User Add & Edit pages to clarify the use of email and password | Text has been added to Web Catalog Manager to clarify the use of email and password fields when Centralized Authentication is being used. |
| FEATURE | SEAL-2983 | Populate ExecuteRuleSet action with rule sets via Entity variables and rule set parameters | The ExecuteRuleSet action dropdown for Entity variables and rule set parameters will now include explicit rule sets. |
| FEATURE | SEAL-3015 | Ability to execute decisions via SDK [documentation] | Decisions can now be executed using irSDK. The documentation for this new feature can be found here: http://support.inrule.com/help/irSdkHelp50/executing_decisions.htm |
| FEATURE | SEAL-3025 | Flagship: 5.7 Documentation fix request | Syntax errors in the InRule Developer Help document have been corrected. |
| FEATURE | SEAL-3091 | Flagship: Make the Decisions icon smaller | Decisions icon in irAuthor has been updated. |
| FEATURE | SFC-48 | InRule for the Salesforce Platform - InRule App Log improvements | The InRule Salesforce App Log contains improvements to provide more information in an organized format, including a full execution time field, the name of the rule set and rule app, and a new "Trace Detail” field that provides information on what entities were changed, request times, and plugin processing steps. |
| FEATURE | SFC-69 | InRule for the Salesforce Platform - Allow for N:1 querying in rule helper filter expression | RuleHelper functionality has been expanded to allow for N:1 querying up to 5 entity levels deep. Further details about deep querying capabilities and its restrictions can be found in the InRule for Salesforce Deployment Guide. |
| FEATURE | SFC-126 | InRule for the Salesforce Platform - Add support for Salesforce OAuth interactive login to irX | Support has been added for interactive login to irX, allowing login without requiring the Salesforce API token and the Consumer Secret/Key. This also enables support for MFA authentication. |
| FEATURE | SFC-128 | InRule for the Salesforce Platform - Enhance rule execution service to support Decisions | The Rule Execution Service now supports Decisions in addition to traditional rules. Decisions still must be run in the context of an entity, requiring an entity as an input. |
| FEATURE | SFC-129 | InRule for the Salesforce Platform - Enhance DecisionClient to be called from Lightning Flow | The InRule DecisionClient is now available to be called from Lightning Flow via the Apex Run Rules action., |
| FEATURE | SFC-135 | InRule for the Salesforce Platform - Add support for Decisions to irVerify within irX for Salesforce | Decisions can now be tested from irVerify. As with the execution service, the Decision must be defined with the root Salesforce entity as the first parameter. Additional parameters are permitted, but they must be primitive datatypes. |
| FEATURE | SFC-139 | InRule for the Salesforce Platform - Add AppDomain caching for RuleHelper queries | RuleHelper queries now support App Domain Caching to help improve query execution time. When the app domain cache timeout is configured, all entities loaded during the execution of RuleHelper queries will remain loaded in cache. This is advantageous for performance sensitive scenarios requiring reference data lookups. To use App Domain Caching, set the "useCaching” parameter to true when querying entities or collections. |
| FEATURE | SFC-140 | InRule for the Salesforce Platform - Add 'Calling InRule from a Lightning Flow' section to Appendix E - Methods for Executing Rules | Appendix E of the Salesforce Deployment Guide has been updated to include a section outlining how to use InRule from a Lightning Flow. |
| FEATURE | SFC-143 | InRule for the Salesforce Platform - Ability for end user to select Rule App Label during Rule Execution request | Support has been added for allowing configuration of Rule Application Label on the Run Rules Lightning Web Component itself. To configure this, a new configuration field has been added to the Run Rules button that accepts a comma-delimited list of rule application labels. For additional guidance on how to leverage this functionality, reference Appendix E of the Salesforce Deployment Guide. |
| FEATURE | SFC-146 | InRule for the Salesforce Platform - Remove CreateEntity from Settings.InfoLevelLoggingTypes | In an effort to reduce clutter and event noise from Info leveling logging on the Rule Execution Service, CreateEntity events are no longer logged. |
| FEATURE | SFC-147 | InRule for the Salesforce Platform - Validate compatibility with Winter '21 release | Updated all API versions used by the framework to v50.0 to add support for Winter '21 functionality. Successfully tested all framework components against a Winter '21 environment. |
| FEATURE | SFC-153 | InRule for the Salesforce Platform - Expose executeRules method for use by custom Lightning components | The DecisionClient now has an exposed method to allow for running rules from custom Lightning web components. For details on how to leverage this, refer to the InRule for Salesforce Deployment Guide. |
| FEATURE | SFC-158 | InRule for the Salesforce Platform - Add entityImage parameter to DecisionClient.executeRules | The DecisionClient now supports passing in a full serialized entity image to the executeRules method. This allows for use of an entity image as it exists at the time of initiating rule execution, rather than querying Salesforce for the entity image during rule execution. |
| FEATURE | SFC-160 | InRule for the Salesforce Platform - Create new ForceClient when opening irVerify and schema import | Fixed a bug that resulted in a session expiration error in irVerify for Salesforce when irAuthor was left open for extended periods of time. |
| FEATURE | SFC-165 | InRule for the Salesforce Platform - RuleHelper configuration to work with native InRule REST execution service | Support has been added for using the RuleHelper with the both native irVerify without the Salesforce extension installed and the InRule flagship execution service. To leverage this, the appropriate assemblies and configurations will need to be made to the irAuthor application and/or the InRule execution service in use. |
| FEATURE | SFC-167 | InRule for the Salesforce Platform - Performance optimization to bulk load salesforce entities in rule execution service | Substantial performance optimizations to bulk loading Salesforce entities have been made to the Rule Execution Service. An average improvement of 10-20x data loading performance has been achieved, depending on entity state size and other factors. These changes also provide a significant reduction to Salesforce API requests. |
| FEATURE | SFC-173 | InRule for the Salesforce Platform - Validate compatibility with Spring '21 Release | Tested irX, rule execution service and Salesforce package against Spring '21 instances. |
| ISSUE | DYN-255 | InRule for Microsoft Dynamics 365 - Null Notifications causing display issues | Resolved a bug that was causing null notifications to prevent all other notifications from displaying. Additionally, null notifications will now appear as an informational notification that says null" |
| ISSUE | DYN-287 | InRule for Microsoft Dynamics 365 - Improve JS error handling (Run Rules button) | Improved error handling around the Run Rules button. Javascript exceptions will now properly be displayed and logged in the plugin trace log. |
| ISSUE | DYN-391 | InRule for Microsoft Dynamics 365 - Error deleting holding solution on package deploy | Resolved the "Error Deleting Holding Solution” commonly encountered when deploying the Dynamics Rule Services Solution via the Powershell script that would require a second deployment to resolve. |
| ISSUE | DYN-454 | InRule for Microsoft Dynamics 365 - IrX: Canceling metadata schema checkout throws an error | Resolved an error that would cause an exception to be thrown when canceling the metadata schema checkout process. |
| ISSUE | DYN-480 | InRule for Microsoft Dynamics 365 - Configuration Test button does not work on-prem | Resolved a bug that was causing the configuration test button to not work properly in on-prem instances. |
| ISSUE | DYN-481 | InRule for Microsoft Dynamics 365 - Handle access exception from deploying online solution to an on-prem Dynamics instance | Attempting to deploy the online solution to an on-prem instance will now throw a more descriptive error. |
| ISSUE | DYN-482 | InRule for Microsoft Dynamics 365 - Package configuration code not running on AppSource deployment | Resolved an issue with AppSource deployment that was causing rule configurations, SAS configurations, and step registrations to be deleted when upgrading the solution. |
| ISSUE | DYN-487 | InRule for Microsoft Dynamics 365 - Running rules with PreOperation update event reverts field changes | Fixed a bug that resulted in field changes from running rules on PreOperation update events to be reverted. |
| ISSUE | DYN-503 | InRule for Microsoft Dynamics 365 - Syncing schema changes from Dynamics that include value list changes results in error if value list not checked out | Resolved a bug that resulted in an error if value list changes from Dynamics attempted to be synced if the value list in irX was not checked out. |
| ISSUE | DYN-504 | InRule for Microsoft Dynamics 365 - Error when creating entity with rules configured for 'OnSave' form event | Resolved a bug when creating entities with rules configured for "OnSave” form events that prevented rules from successfully executing. |
| ISSUE | DYN-523 | InRule for Microsoft Dynamics 365 - Sdk is not defined error when running rules on form against new entity | Resolved a bug that caused running rules from javascript against new, unsaved entities to fail. |
| ISSUE | DYN-536 | InRule for Microsoft Dynamics 365 - Including multi-select picklist field on ruleapp schema returns error from execution service | Fixed a bug that caused all rule execution to fail if a multi-select picklist field was included on the schema. |
| ISSUE | DYN-545 | InRule for Microsoft Dynamics 365 - Error when updating schema for rule app with MultiSelect | Fixed a bug that caused schema updates to not work properly when the rule app included a multiselect picklist field. |
| ISSUE | SEAL-2591 | irAuthor TestService needs a public Test method that takes a Decision parameter | A new overload on the test service was added to allow Decision inputs to be passed in. In addition, a new method was added to the Decision class in the irSDK to load inputs before executing. |
| ISSUE | SEAL-2616 | Set ie version registry key on irx install | The installer has been updated to set the IE version registry key. |
| ISSUE | SEAL-2926 | irAuthor locks up when using Centralized Auth | This error has been resolved. An exception will no longer be thrown when using Centralized Authentication within irAuthor. |
| ISSUE | SEAL-3207 | Flagship: Rule Tracing in .NET Core apps and error in irVerify | File-based rule tracing now works in .NET Core apps using irSDK. In addition, error thrown when executing rule traces in irVerify has been fixed. |
| ISSUE | SFC-122 | InRule for the Salesforce Platform - IrX: Error when canceling schema Import | Resolved an error that would cause an exception to be thrown when canceling the metadata schema checkout process. |
| ISSUE | SFC-145 | InRule for the Salesforce Platform - InRule configuration tabs in app do not show up if 'my domain' is not enabled | The InRule Lightning component tabs have been updated to VisualForce pages to provide access to them without needing to enable the "My domain” option. These tabs should now be visible by default. |
| ISSUE | SFC-154 | InRule for the Salesforce Platform - Numbers less than 0.0001 cause "Input string was not in a correct format" error when running rules | Fixed a bug that caused rule execution to fail if a number field had a value of less than 0.0001. |
| ISSUE | SFC-171 | InRule for the Salesforce Platform - Persistence Error when saving Datetime fields | Fixed a bug that resulted in a persistence error being thrown when attempting to persist changes to DateTime fields during rule execution. |
InRule Decisioning Version 5.7.0 Release Notes
- Updated
Comments
0 comments
Please sign in to leave a comment.