| Type | Case ID | Summary | Description |
| FEATURE | DYN-267 | InRule for Microsoft Dynamics 365 - Update irX and rule execution service Dynamics sdk to xrm 9.1.0.42 | Updated the version of the Microsoft Dynamics SDK version used by irX and the execution service to 9.1.0.42 to support additional functionality |
| FEATURE | DYN-412 | InRule for Microsoft Dynamics 365 - Enable RuleHelper to be configured/used from flagship (non-Dynamics) execution service | Added support for using the Dynamics RuleHelper with flagship (non-Dynamics) execution service |
| FEATURE | DYN-416 | InRule for Microsoft Dynamics 365 - ARM Template improvements for Relay check, deploy from portal, other | The ARM Template for deploying Azure resources has been updated to allow for SaaS deployment through the Azure portal interface, in addition to the existing Azure CLI and Powershell support. |
| FEATURE | DYN-417 | InRule for Microsoft Dynamics 365 - Extend InRule integration scenarios for the Microsoft Power Platform | The InRule for Dynamics 365 Deployment Guide has been updated to contain a new content section detailing how to integrate with the different components of Microsoft’s Power Platform. This section provides samples of how to integrate with both model driven applications and canvas applications, as well as showing how to set up Power Automate and leverage it alongside canvas applications to execute rules. |
| FEATURE | DYN-418 | InRule for Microsoft Dynamics 365 - Add 'Test' button to Config Page for round-trip relay/execution service test ping | Added a “Test Connectivity” button in the Rule Services Solution to provide a further upstream means of verifying proper configuration of the solution and supporting Azure resources. This “Test Connectivity” button will verify basic execution service connectivity to Dynamics. |
| FEATURE | DYN-420 | InRule for Microsoft Dynamics 365 - Deployment Guide Updates | The InRule for Dynamics 365 Deployment Guide has been updated for relevancy and expanded to include additional content, chiefly oriented around using InRule with the various application types within the Microsoft Power Platform. |
| FEATURE | DYN-421 | InRule for Microsoft Dynamics 365 - Return Dynamics and Catalog connectivity info in service test | The “Test Connectivity” feature within the Dynamics Rule Services Solution has been expanded to conduct additional checks to provide verification on a wider breadth of configurations. The button will now verify that the execution service can connect to Dynamics and the catalog. |
| ISSUE | DYN-425 | InRule for Microsoft Dynamics 365 - UCI displays notifications in opposite order of classic UI | Resolved a bug that caused notifications in UCI to display in the reverse order of how they were fired. |
| FEATURE | DYN-426 | InRule for Microsoft Dynamics 365 - Update ARM templates to support app service plan in different resource group | Resolved an issue with the ARM template for deploying out the requisite Azure resources for the Dynamics solution that prevented the usage of existing App Service Plans that reside in a different resource group from where the template is deploying its resources to. |
| FEATURE | DYN-428 | InRule for Microsoft Dynamics 365 - Load in-progress collections in plugin and execution service | increase {{MaxReceivedMessageSize}} to 100 MB |
| ISSUE | DYN-429 | InRule for Microsoft Dynamics 365 - Ensure entity updates occur before status change in plugin persistence | Implemented an alteration to order of operations for rules altering an entity’s status. Prior to this change, rules where an entity is updated and then resolved would not properly execute, as the command to set the entity’s status to resolved was executing first, making the entity read-only and unable to be updated. The order of operations has been altered to insure updates occur before the resolution of the entity, allowing for rules using this model to function properly. Due to the read-only nature of resolved entities however, this change does implement in the reverse problem. Rules attempting to re-open a resolved entity and then update it will no longer function. |
| ISSUE | DYN-432 | InRule for Microsoft Dynamics 365 - Fix regression in related entities logging for data loading | Resolved an issue where related entity names and their loading times were not being properly logged by the execution service to Azure application logs and Application Insights. |
| ISSUE | DYN-439 | InRule for Microsoft Dynamics 365 - Fix regression in 1:n reflexive relationship loading | Fixed a bug that caused 1:n self-referential relationships to not load properly. |
| FEATURE | DYN-442 | InRule for Microsoft Dynamics 365 - Add Dynamics sdk advanced login control to irX environment manager | Added support for advanced authentication, including MFA, to irX login. |
| FEATURE | DYN-444 | InRule for Microsoft Dynamics 365 - Validate compatibility with Dynamics 365/PowerPlatform 2020 Release Wave 1 | Validated InRule’s compatibility with Dynamics/CDS 2020 release wave 1. |
| FEATURE | SEAL-1846 | Check decisions during rule app validation | Decisions are now checked for errors during validation. |
| FEATURE | SEAL-2155 | irAuthor Click-Once is automatically configured for Centralized Authentication | Centralized Authentication has been enabled for users using irAuthor via the trial. |
| FEATURE | SEAL-2156 | Trial user is able to reset their password | The password reset flow has been enabled for users in trials. |
| FEATURE | SEAL-2160 | Remove publish button from irAuthor by default | The Publish Decisions button in the irAuthor ribbon has been removed. To execute decisions using irServer Rule Execution Service, please see information in the InRule Developer Help file under irServer Rule Execution Service REST Endpoint - Execute Decision |
| FEATURE | SEAL-2284 | Add runtime support for Decisions to irServer | Runtime support has been added for Decisions in irServer. |
| FEATURE | SEAL-2292 | Hide Rule Flows by default in the Navigation Pane | Rule Flow navigation pane in irAuthor is now hidden by default on new installs with option to enable. This can be done in the options screen found in the menu in the bottom of the Navigation Pane. Existing installs and upgrades will respect the current state of the pane. |
| FEATURE | SEAL-2340 | Upgrade Flagship to .NET 4.7.2 | irAuthor, irCatalog, irServer, and full framework irSDK have been updated to .NET v4.7.2 from .NET v4.6.1. |
| FEATURE | SEAL-2348 | Enable endpoint overrides in irServer Rule Execution Service | EndPoint and Data Element overrides may now be configured in irServer Rule Execution Service via configuration AppSettings instead of being sent in the request. These AppSettings may also be overridden by ConfigurationBuilders defined in the .config file. |
| FEATURE | SFC-93 | InRule for the Salesforce Platform - Create salesforce app component and content components | Added an app component to the InRule for Salesforce app that provides a new content tab with details of how to get started setting up and using the solution. |
| FEATURE | SFC-96 | InRule for the Salesforce Platform - Update DecisionClient to respect user-context CRUD and FLS permissions | Updated rule execution to respect user and field level permissions. Users with insufficient permissions to alter fields or entities will no longer be able to alter them via rules. |
| FEATURE | SFC-99 | InRule for the Salesforce Platform - InRule App Content Updates | Updated and enhanced the InRule for Salesforce app content pages, breaking them out into the following sections for improved readability and reference: -Getting Started -Configuration -Running Rules |
| FEATURE | SFC-101 | InRule for the Salesforce Platform - Add connectivity test button to Configuration tab | Added a “Test Connectivity” button to the Configuration tab of the InRule for Salesforce App that provides users a further upstream validation that their InRule resources are properly configured and connected. The Test Connectivity button will verify connectivity between the execution service and Salesforce, as well as the execution service and the catalog and provide appropriate feedback in the cases of connection successes or failures. |
| FEATURE | SFC-102 | InRule for the Salesforce Platform - AfterInsert and other Trigger enhancements | Support for executing rules via triggers has been expanded to allow for usage of After Insert triggers alongside the existing support for After Update triggers. |
| FEATURE | SFC-103 | InRule for the Salesforce Platform - Add support for dirty entity image to decision client and execution service | Executing rules via triggers now supports passing in-progress entity images rather than querying for the entity image from the rule execution service. This allows for insuring the state of the entity during rule execution despite the asynchronous nature of trigger execution. |
| FEATURE | SFC-105 | InRule for the Salesforce Platform - Error In Decision Client when no Named Credential is configured | Fixed issue that was causing no exception to be thrown to Salesforce in events where no Named Credential was present. If rule execution is attempted without a Named Credential, an error message will now be returned alerting the user to the lack of Named Credential. |
| FEATURE | SFC-111 | InRule for the Salesforce Platform - ARM Template improvements for SaaS deploy and other | The ARM Template for deploying Azure resources has been updated to allow for SaaS deployment through the Azure portal interface, in addition to the existing Azure CLI and Powershell support. |
| FEATURE | SFC-114 | InRule for the Salesforce Platform - Update Salesforce Application page content | Content in the InRule for Salesforce App “Getting Started” and “Configuration” sections has been updated for increased accuracy and detail. |
| ISSUE | DYN-409 | InRule for Microsoft Dynamics 365 - irX Entity search error when entity does not exist in selected environment | The Search button in irX has been disabled when attempting to perform an entity search in irX with no view selected to prevent resulting issues. |
| ISSUE | SEAL-1727 | Can't reorder inputs/outputs | Enabled ordering of inputs and outputs for Decisions in irAuthor. |
| ISSUE | SEAL-1847 | Decisions over 255 characters should not pass validation | Validating a rule application that has a Decision with a name longer than 255 characters results in a validation error based on the long decision name. |
| ISSUE | SEAL-1899 | Set Field Invalid action without message doesn't cause validation error when in a decision rule set | Set Field Invalid actions on a Decision now raise a validation error if the message is missing. |
| ISSUE | SEAL-2200 | Loading trial the first time is taking too long | Added a spinner to the trial to let user know that loading is in progress. |
| ISSUE | SEAL-2201 | No feedback when incorrect credentials are entered multiple times on new login page in trial | Updated login page to provide feedback when login credentials are invalid in trials. |
| ISSUE | SEAL-2222 | Update .NET core documentation with latest license information | .NET core documentation has been updated with the latest license information |
| ISSUE | SEAL-2264 | Update user icon color scheme | Updated the color scheme for the user icons on the Portal |
InRule Decisioning Version 5.6.0 Release Notes
- Updated
Comments
0 comments
Article is closed for comments.