| Type |
Case ID |
Summary |
Description |
| FEATURE |
DYN-154 |
InRule for Microsoft Dynamics 365 - Enable updating of status in rule apps |
Updating an entity's status via rules now has limited support. Currently, only entities with "simple" status switches (Active,/Active) and the Case/Incident entity are supported. Specifically when updating Case via rules will result in a hard-set Resolution Description of "Resolved by Rules." This description can be altered manually after the fact, but dynamically setting the resolution description at time of running rules is not supported at this time. |
| FEATURE |
DYN-303 |
InRule for Microsoft Dynamics 365 - Enable endpoint overrides via AppSettings Config |
The InRule Dynamics solution now supports Endpoint Overriding via App Settings on the Rule Execution AppService. For a detailed explanation on how to use endpoint overrides, please reference the new Appendix G: Endpoint Overrides in the latest version of the InRule for Dynamics 365 Deployment Guide. |
| FEATURE |
DYN-324 |
InRule for Microsoft Dynamics 365 - Error message from execution service uses Dynamics entity Name instead of Display Name |
Errors returned by the execution service to Dynamics will now use the entity's InRule schema name rather than their Dynamics logical name, as they did before. |
| FEATURE |
DYN-336 |
InRule for Microsoft Dynamics 365 - Provision app insights resource from arm template |
The ARM Template provided with the Dynamics solution for deploying out all the relevant Azure resources now provides the capability of deploying an App Insights resource. If you wish to create one, simply define the resource's name for the "appInsightsResourceName" parameter and the template will create the resource with that name, as well as associate its instrumentation key with your Rule Execution App Service. If you have a pre-existing AppInsights resource you would prefer to associate your AppService with, you can leave the AppInsightsResourceName parameter blank, and fill in the appInsightsInstrumentationKey parameter with the instrumentation key of your existing AppInsights resource instead. |
| FEATURE |
DYN-339 |
InRule for Microsoft Dynamics 365 - Add RunRules button on View pages |
The Run Rules button is now available on the Entity View page. To use it, insure your Run Rules button is enabled for the given rule configuration associated with the entity type you wish to run against. Then simply select the checkboxes next to the entity or entities you wish to run rules against, then hit Run Rules. The dropdown box for multiple rule sets is also compatible with this button. Rules can only be executed to a single page of entities at a time, with a hard entity limit of 50. |
| FEATURE |
DYN-374 |
InRule for Microsoft Dynamics 365 - Update rule helper NtoN methods |
The LoadMappedNtoNCollection RuleHelper method has been depreciated, as its functionality is redundant with that of the LoadMappedChildCollection method. The LoadMappedChildCollection method has been updated to support NtoN queries, including self-referential NtoN queries. All useage of the LoadMappedNtoNCollection method should be migrated to using the LoadMappedChildCollection method instead. |
| FEATURE |
DYN-375 |
InRule for Microsoft Dynamics 365 - Error handling issue for malformed On-prem connection string |
Resolved a bug in the on-prem solution that was causing a generic error to be thrown rather than the proper "Invalid Connection String" error in circumstances where the on-prem connection string did not properly define a domain name. |
| FEATURE |
SEAL-1789 |
InRule.Repository.Extensions does not get the correct version information |
InRule.Repository.Extensions now ships with the correct version information. |
| FEATURE |
SFC-73 |
InRule for the Salesforce Platform - Enable AppInsights deployment, logging, and configuration |
The Salesforce rule execution service now supports logging to Azure AppInsights resources in addition to the existing Azure Application Log. To log to an AppInsights resource, simply add the "inrule:logging:appInsights:instrumentationKey" AppSetting to your Rule Execution Service and define its value as the instrumentation key of an existing AppInsights resource. Additionally, the ARM Template provided with the Salesforce solution for deploying out all the relevant Azure resources now provides the capability of deploying an AppInsights resource. If you wish to create one, simply define the resource's name for the "appInsightsResourceName" parameter and the template will create the resource with that name, as well as associate its instrumentation key with your Rule Execution App Service. If you have a pre-existing AppInsights resource you would prefer to associate with your new AppService that will be created by the template , you can leave the AppInsightsResourceName parameter blank, and fill in the appInsightsInstrumentationKey parameter with the instrumentation key of your existing AppInsights resource instead. |
| FEATURE |
SFC-77 |
InRule for the Salesforce Platform - Classic UI DecisionClientHelper javascript resource |
Overhauled the sample Run Rules Javascript buttons for the Salesforce Classic View for improved readability and improved ease of use as a template for the creation of custom run rules buttons. For using the sample buttons as a template for making custom buttons, all that now needs to be done is to edit the values within the "config" object defined in the Javascript. For a more in-depth overview of these changes, please reference the latest version of the InRule for Salesforce Deployment Guide. |
| FEATURE |
SFC-79 |
InRule for the Salesforce Platform - Send only changed fields back from execution service |
Rather than send back the entire entity image containing all fields in the entity, the Salesforce rule execution service will now only send back fields that have been updated. This resolves several bugs that were being encountered during rule execution. |
| FEATURE |
SFC-80 |
InRule for the Salesforce Platform - Enable Endpoint Overrides via AppSettings Config |
The InRule Dynamics solution now supports Endpoint Overriding via App Settings on the Rule Execution AppService. For a detailed explanation on how to use endpoint overrides, please reference the new Appendix G: Endpoint Overrides in the latest version of the InRule for Dynamics 365 Deployment Guide. |
| FEATURE |
SEAL-1579 |
Decision Services Milestone 3 (M3) |
Decision Services give you a decision-centric authoring experience that is simpler to author, simpler to publish as a service, and simpler to consume using industry standard techniques. |
| ISSUE |
DYN-365 |
InRule for Microsoft Dynamics 365 - Execute rules for entities containing fields of type EntityCollection throws errors |
Resolved a bug encountered when running rules on entities that contained fields of type EntityCollection when Return Full Entity Image was set to true, or one of the fields was being updated via rule. These fields, most commonly found on Activity type entities (such as Email), can no longer be altered via rules; this does not change existing irAuthor behavior, as these fields were already excluded, but they can no longer be affected within Dynamics itself. |
| ISSUE |
DYN-386 |
InRule for Microsoft Dynamics 365 - Return Full Entity Image throws error when called from workflow activity |
Resolved a bug with running rules from custom workflows that caused rule execution to fail when Return Full Entity Image was set to true on the rule configuration. |
| ISSUE |
SEAL-1805 |
irWord for Word 365 does not work with v5.4.3 updated InRule.Authentication.dll |
irWord support has been restored. |
| ISSUE |
SFC-74 |
InRule for the Salesforce Platform - Classic UI Run Rules button on Contact shipped with solution executes Account/AccountDefaultRules |
Resolved an error in the Salesforce package with how the sample Run Rules classic view Javascript button for Contact was configured. Rather than erroneously attempt to run rules against Account, it should now properly run rules against Contact. |
| ISSUE |
SFC-75 |
InRule for the Salesforce Platform - Errors running rules from Contact in Lightning and Classic |
Resolved a bug encountered when executing rules against the Contact entity that was a result of allowing rules to attempt to update the computed fields (such as Full Name). This has been resolved and now computed fields can no longer be directly updated; rather, the fields that the computed field references must be updated to affect the computer field. For example, to update the Full Name field, you would need to update First Name and/or Last Name via rules. |
| FEATURE |
SFC-29 |
InRule for the Salesforce Platform - Add support to DecisionClient for update triggers |
A new method has been added to the DecisionClient that supports calling from triggers. At this time only after update triggers are supported. |
| FEATURE |
DYN-344 |
InRule for Microsoft Dynamics 365 - Allow rule services solution components to be deployed to PowerPlatform environments without Dynamics CE |
The Rule Services Solution can now be deployed to arbitrary model-driven Microsoft PlowerPlatform environments that don't have Dynamics Customer Engagement installed. This can be accomplished via either AppSource or the deployment script, identical to deploying to Dynamics. |
| FEATURE |
DYN-366 |
InRule for Microsoft Dynamics 365 - Add support to irx and plugin saving for 'other' side of self-referencing n:n |
irX and the Dynamics Rule Services Solution now support loading and executing rules against entities that have n-to-n relationships with themselves, or "self-referential" n-to-n relationships. They can be loaded via the irX schema picker. |
| FEATURE |
DYN-378 |
InRule for Microsoft Dynamics 365 - Support pre-operation execution stage for create message |
Amended rule execution logic to support pre-operation execution for rules running on create meassages. In scenarios where create and update messages are registered to the same entity and rules are set to run on create, these changes will now happen within the same create transaction rather than triggering an additional update message after the create. |
| FEATURE |
DYN-389 |
InRule for Microsoft Dynamics 365 - Duplicate tooltip when Run Rules button contains multiple rulesets |
Resolved a bug encountered with the Run Rules button in the Classic UI that resulted in the Run Rule button's tooltip displaying twice. |
| FEATURE |
DYN-393 |
InRule for Microsoft Dynamics 365 - 'Cannot insert duplicate key' error when attempting entity inserts, even when ruleapp contains no inserts |
Resolved a bug caused by rules being run against entities with collections on them being treated as inserts, resulting in a "Cannot insert duplicate key" error being thrown. |
| FEATURE |
SEAL-1590 |
Remember Rule Version column sorting |
The column sort order of version grids may be persisted in the rule application to give consistent view across all versionable elements. |
| FEATURE |
SEAL-1913 |
Add assertion test for "Rule Not Fired" |
Added an assertion to the irVerify Regression Tester that tests "Rule Not Fired". It behaves the opposite of the "Rule Fired" assertion. |
| FEATURE |
SEAL-1982 |
Add cut, copy, paste, and duplicate to the regression tester test suite tree |
irVerify Regression Tester now allows cut, copy, paste, move-up, move-down, and duplicate operations on the Test context-menu. |
| FEATURE |
SEAL-1984 |
Add new assertion "Notification contains text...", where it would assert on certain text appearing in a notification. |
Added an assertion to the irVerify Regression Tester that tests whether a given notification contains specific text. |
| FEATURE |
SEAL-1987 |
Add assertion to compare a date field to the current date (Now) |
Added an assertion to the irVerify Regression Tester to compare a Date Field to the current date. |
| FEATURE |
SEAL-1988 |
Add assertion tests where you can compare two fields |
irVerify Regression Tester now supports assertions that can compare one Field to another Field. |
| FEATURE |
SEAL-2014 |
Resize IrAuthor login window to not be needlessly large |
The Centralized Authentication login window in irAuthor and irCatalog Manager has been reduced to a more appropriate size. |
| FEATURE |
SEAL-2018 |
Add new assertion "Notification contains text in any notification" |
Added an assertion to the irVerify Regression Tester that verifies that any notification contains specific text. |
| FEATURE |
SFC-85 |
InRule for the Salesforce Platform - Update form UI when rules are run on update trigger |
If an update trigger is registered to an entity, and the trigger invokes the supported method on the DecisionClient, users who update entities from forms will now receive UI notifications and a form refresh when rules complete, similar to the existing functionality when running rules from the included lighting component. |
| FEATURE |
SFC-88 |
InRule for the Salesforce Platform - Allow overriding of rule app when calling DecisionClient |
In addition to setting the custom config object included with the package, the Rule App can now also be passed as an additional parameter when calling the DecisionClient at run time. An additional configuration field has also been added to the included Lightning component to support setting this value. |
| ISSUE |
DYN-394 |
InRule for Microsoft Dynamics 365 - Incorrect Error Message in Step Registration Configuration |
Resolved a bug that resulted in a superfluous error message appearing in scenarios when a user had not selected an SDK message when creating a new plugin step. |
| ISSUE |
DYN-404 |
InRule for Microsoft Dynamics 365 - irX/irVerify entity search error on ServiceActivity entity |
Resolved a bug encountered when launching irVerify from the ServiceActivity entity that resulted in irVerify being unable to connect to Dynamics and throwing an error. |
| ISSUE |
SEAL-1487 |
Notification Fired Assertion Test in Test Suite does not show Notifications in Else statements |
Creating "Notification Fired" assertions can now be created inside Else blocks in irVerify Regression Tester. |
| ISSUE |
SEAL-1596 |
Fix Remaining Windows for - [irAuthor does not honor pinned items and window locations/sizing between sessions (close and open)] |
The position and size of irAuthor's Points of Interest, Advanced Find, and Find tool windows are now remembered. |
| ISSUE |
SEAL-1912 |
Regression tester cannot process "rule fired" assertion test |
Fixed an assertion in the irVerify Regression Tester that tests "Rule Fired". |
| ISSUE |
SEAL-1921 |
Test Suite throws error when trying to expand a test folder (bug introduced in 5.4.1) |
Expanding a Test folder in irVerify Regression Tester no longer raises an error. |
| ISSUE |
SEAL-1929 |
Missing Centralized Auth DLLs in Azure App service package. |
Azure App Services package now correctly contains libraries to support Centralized Authentication. |
| ISSUE |
SEAL-1933 |
Add 'Contains' Assertion to the Regression Tester |
Added a "Contains" assertion to the irVerify Regression Tester that tests whether one string contains another string. |
| ISSUE |
SEAL-2009 |
Decisions with the same entity as input/output produces duplicate entries in ruleset lists |
A Decision now supports fields that have the same name for the input field and output field. By naming an output field as the same name as an input field (or vice versa), the two fields become the same field that is both an input to the Decision as well as the output of the Decision. |
| ISSUE |
SEAL-2013 |
Inrule.Authoring.Authentication nuget package is missing from installer and not being posted to Nuget.org |
The InRule.Authoring.Authentication NuGet package is now installed correctly when the user installs the SDK. |
| ISSUE |
SEAL-2082 |
irAuthor does not preserve nav panel button order when older version has been used |
Resolved a bug that caused the Decisions navigation panel button to appear at the bottom of the navigation when a version of irAuthor prior to v5.5.0 was used previously. |
| ISSUE |
SFC-89 |
InRule for the Salesforce Platform - SF Read-Only Fields not showing as Read-Only in irAuthor |
When importing entity fields into a rule app schema with irx, all fields that are read-only in SalesForce will be correctly marked as read-only in the field schema. Auto-number and calculated were already being marked as read-only, but this update covers any other fields with an Updateable value of false. |
| FEATURE |
DYN-396 |
InRule for Microsoft Dynamics 365 - Improvements for bulk data and entity loading |
Reduced amount of data requested during intitial entity load, and fixed an issue when loading customer and owner entities. |
Comments
0 comments
Article is closed for comments.