| Type |
Case ID |
Summary |
Description |
| FEATURE |
DYN-189 |
InRule for Microsoft Dynamics 365 - Document solution upgrade process in Deployment Guide Appendix |
Added a new appendix to the InRule for Microsoft Dynamics Deployment Guide providing details on the process for upgrading InRule versions. |
| FEATURE |
DYN-232 |
InRule for Microsoft Dynamics 365 - Notifications no longer persist between rule calls |
Notifications returned by the rule service will now clear themselves if the user runs rules again without refreshing page, and any new notifications returned will take their place. |
| FEATURE |
DYN-239 |
InRule for Microsoft Dynamics 365 - Update Integration Role to read-only |
The InRule Integration Role used for S2S authentication between the Rule Execution Service and Dynamics no longer requires global read-write privileges to all Dynamics entities and now only requires read-only permissions to all Dynamics entities. |
| FEATURE |
DYN-241 |
InRule for Microsoft Dynamics 365 - Formalize validation patterns and update cancellation in framework |
Added an additional method to further support execution of rules via custom javascript. |
| FEATURE |
DYN-243 |
InRule for Microsoft Dynamics 365 - Validation Error messages are shown in the notification bar |
Validation errors returned by the Rule Execution Service will now be fully displayed in the Notification banner on the entity page rather than being truncated |
| FEATURE |
DYN-244 |
InRule for Microsoft Dynamics 365 - S2S authentication setup steps for SaaS deployment |
The InRule for Microsoft Dynamics Integration Guide now contains a new Appendix detailing how to properly configure S2S authentication for SaaS deployments. |
| FEATURE |
DYN-256 |
InRule for Microsoft Dynamics 365 - Ability to specify the App Service Plan name in the azuredeploy.parameters.json |
The App Service Plan name has been exposed in the ARM template parameters file to simplify customizing the Plan name for Azure deployments. |
| FEATURE |
DYN-257 |
InRule for Microsoft Dynamics 365 - Improve error message for incorrect catalog username/password |
Added improved error handling for scenarios where the catalog username/password is incorrect to make it more apparent what the problem is. |
| FEATURE |
DYN-258 |
InRule for Microsoft Dynamics 365 - Remove created, modified, and organization fields from Rule Config import |
The "Created On" and "Modified On" fields have been removed from the configuration entity schema to resolve issues arising from incompatibilities between US and non-US date formatting. |
| FEATURE |
DYN-262 |
InRule for Microsoft Dynamics 365 - Rule solution compatibility with April 9.1 Release for Dynamics Unified Interface (UCI) |
Added full support for running rules from the UCI. |
| FEATURE |
DYN-263 |
InRule for Microsoft Dynamics 365 - Provide 8.2 on-prem Dynamics solution deployment packages |
A new Dynamics On-Prem v8.2 compatible solution is now available for users that have not yet upgraded to On-Prem v9.0. This 8.2 compatible solution lacks the RuleHelper multi-select query functionality found in the v9.0 solution. The InRule for Microsoft Dynamics Integration Guide provides guidance on how to deploy the v8.2 compatible solution. |
| FEATURE |
DYN-273 |
InRule for Microsoft Dynamics 365 - Run Rules throws error on new saved entity without page reload |
Resolved a bug that resulted in the error 'No Entity ID passed in input parameters' to be thrown in instances where an entity was created, saved, and had rules run against it before the page was refreshed when DirtyEntityImage was disabled. Rules should now properly execute against entities that have just been saved without requiring a full page refresh. |
| FEATURE |
DYN-274 |
InRule for Microsoft Dynamics 365 - Support for up to 10 entity references for RH query filters |
Expanded existing RuleHelper functionality to support referencing up to 10 entities in any given query, up from 4. |
| FEATURE |
DYN-275 |
InRule for Microsoft Dynamics 365 - Truncate RuleResponse in Trace Log |
Changed trace logging surrounding the Rule Response body. The Rule Response will now no longer be displayed if the execution log is enabled. If it is not enabled, the Rule Response will be truncated after 6000 characters. This change is to prevent an issue where Rule Responses exceeding a certain length would lead to the beginning of the log being truncated in order to fit within the log's character limit. |
| FEATURE |
DYN-277 |
InRule for Microsoft Dynamics 365 - Add select all field and children to irx |
Added a "Select All" button that allows users to select all fields or children for a given entity with a single button press. |
| FEATURE |
DYN-280 |
InRule for Microsoft Dynamics 365 - Document patterns calling InRule from javascript events |
Appendix E of the InRule for Dynamics Deployment Guide has been expanded to provide more detail around how to properly call InRule from Javascript events. |
| FEATURE |
DYN-290 |
InRule for Microsoft Dynamics 365 - AppDomain caching for RuleHelper queries |
RuleHelper queries now support App Domain Caching to help improve query execution time. When app domain caching is flagged for use, all entities loaded during the execution of RuleHelper queries will remain loaded in cache, removing the need for them to be loaded again, until the cache is cleared. How long entities will be held in cache before they are cleared is configurable. To use App Domain Caching, set the "useCaching" parameter to true when querying entities or collections. An example of how to do this has been included in the new DynamicsRules sample rule app. |
| FEATURE |
DYN-296 |
InRule for Microsoft Dynamics 365 - AppDomain Cache configuration setting |
Added a new configuration setting that allows users to define how long to persist entities held in the AppDomain Cache before the cache is cleared. A help tooltip has been included with this configuration setting to provide guidance on configuring this setting. |
| FEATURE |
DYN-304 |
InRule for Microsoft Dynamics 365 - Additional RuleHelper query examples in DynamicsRules ruleapp |
Applied fixes to existing example rules and added additional examples to the DynamicsRules sample rule app bundled with the solution. It now includes example rules for how to leverage the App Domain Cache and how to load mapped child collections. |
| FEATURE |
DYN-311 |
InRule for Microsoft Dynamics 365 - ARM templates for Catalog and Execution Service |
ARM Templates have been created for the InRule Catalog Service and Flagship Execution Service. These templates include parameter files for easy configuration of the relevant Azure resources deployed by the templates. For guidance on how to leverage these templates, refer to the new deployment documentation found here: |
| FEATURE |
DYN-312 |
InRule for Microsoft Dynamics 365 - Option to deploy app service with 64-bit in ARM template |
Added a configuration option to the Dynamics and Flagship ARM templates that allows for the option to deploy the app service to 64 bit. |
| FEATURE |
DYN-314 |
InRule for Microsoft Dynamics 365 - Enhance Entity Loading Cache and Info Logging |
Streamlined entity loading cache event logging to provide a more clear picture of the number of times an entity or collection has been loaded on a given relationship. |
| FEATURE |
DYN-319 |
InRule for Microsoft Dynamics 365 - 'Perisist Changes' RulesConfiguration setting moved to the 'Plugin' section |
Reorganized the Dynamics plugin configuration options by moving "Persist Changes" out from underneath the "Run Rules Button Options" header and placing it under the "Plugin" section. |
| FEATURE |
DYN-320 |
InRule for Microsoft Dynamics 365 - Save existing custom action registrations during solution upgrade |
Registered custom action steps will now be persisted when the Dynamics Rule Service Solution is upgraded to a new version, as opposed to being wiped. |
| FEATURE |
DYN-328 |
InRule for Microsoft Dynamics 365 - App Insights and Event Log Configuration Options |
Basic configuration for leveraging Azure AppInsights has been added for the Dynamics Execution Service. To log to AppInsights, the app setting "inrule:logging:appInsights:instrumentationKey" will need to be added to your app service, with its value set to the instrumentation key of your existing AppInsights resource. Regardless of whether or not this setting is configured, logs will continue to be logged to the Application Event Log as well. |
| FEATURE |
DYN-351 |
InRule for Microsoft Dynamics 365 - Preserve Default Rule Configuration entity state for upgrades |
Fixed an issue where re-deploying the solution would overwrite the existing Default Rule Configuration record. Values from the existing record are now automatically copied out and replace after solution import is complete. |
| FEATURE |
SEAL-1439 |
Remove InRule for Microsoft Azure Cloud Service Packages |
InRule for Microsoft Azure Cloud Service Packages has been deprecated and is no longer available in the installer. |
| FEATURE |
SEAL-1456 |
Catalog Upgrader fails to upgrade and throws error for customer who has XACT_ABORT enabled in SQL Server |
Fixed an issue where catalog upgrades would fail if SQL Server had the XACT_ABORT setting enabled. There is now a configuration setting that can be enabled to allow upgrades when XACT_ABORT is enabled. |
| FEATURE |
SEAL-1457 |
JSON Schema Import Fails |
Fixed an issue where importing schema using the JSON Snippit import functionality in IrAuthor would fail. |
| FEATURE |
SEAL-1460 |
MaxReceivedMessageSize webservice override is not available in irVerify endpoint override screen |
The MaxReceivedMessageSize property is now available to be overridden via the IrVerify Endpoint Override Options screen. |
| FEATURE |
SEAL-1461 |
Catalog time-out error occurs and causes background compile to not work |
The irServer Rule Execution Service will now respect the "connectionTimeout" setting in the web.config or app.config configuration files when using catalog-based rule applications. Prior to this release, if the "ConnTimeout" value was not specified for a specific request, the default value of 60 seconds was used. It will now fallback to the "connectionTimeout" setting which applies to all requests. If that value is not specified in the web.config or app.config configuration file, then the default value will be used. |
| FEATURE |
SEAL-1462 |
Improve Versioning usability in irAuthor |
The Versions, Attributes, and Notes tool window tabs now show a visual count indicator if they contain any items. |
| FEATURE |
SEAL-1463 |
SalesForce Rules Helper needs to be included as a part of the Installer package for IrX |
RuleHelper assemblies are now automatically installed into the EndPointAssemblies folder of irAuthor when installing irX for the Salesforce Platform component. |
| FEATURE |
SEAL-1470 |
Customer is trying to use Test Suite but it's so slow for them, it's practically unusable. |
Improved performance for navigating a Test Suite in irVerify. |
| FEATURE |
SEAL-1477 |
Create an irVerify experience to view metrics |
A Metrics tab has been added to irVerify. It displays the final values of any fields, calculations, and conditions that have been flagged as metrics in irAuthor. |
| FEATURE |
SEAL-1478 |
Add Metrics |
InRule Metrics provides the ability to log field and rule values directly from the engine to a data store of your choosing. |
| FEATURE |
SEAL-1496 |
Verify Metrics documentation in the release |
Metrics documentation has been added to InRule's help documents. |
| FEATURE |
SEAL-1497 |
Update NuGet packages to contain license file rather than license URL |
Due to a request by [NuGet.org|http://NuGet.org], the license URL on NuGet packages has been replaced with a local license file. |
| FEATURE |
SEAL-1501 |
Rule Version column sorting |
Added sorting on version name, effective date and created date to rule versions in irAuthor. |
| FEATURE |
SEAL-1533 |
Add StackOverflow.txt to Licenses directory |
A new file "StackOverflow.txt" has been added to the "Licenses" directory of an InRule installation. This file contains attribution for snippets from Stack Overflow that InRule has used. |
| FEATURE |
SEAL-1534 |
Add CodeProject.txt to Licenses directory |
A new file Code.txt has been added to the "Licenses" folder of an InRule installation. This file contains attribution for the snippets that InRule has used from the Code Project. |
| FEATURE |
SEAL-1622 |
Centralized Auth Milestone 2 |
Added functionality to customer SaaS instances to allow the usage of our centralized authentication provider. |
| FEATURE |
SEAL-1626 |
Add support for CA to Portal |
Added the ability for the Portal web application in SaaS instances to use our centralized authentication provider. |
| FEATURE |
SEAL-1627 |
Add support for CA to REC |
Added the ability for the Rule Execution Console web application in SaaS instances to use our centralized authentication provider. |
| FEATURE |
SEAL-1633 |
Update Flagship to build against latest .NET Core 3.0.100 |
Updated .NET Core build to use .NET Core 3.0.100. |
| FEATURE |
SEAL-1660 |
Centralized Authentication - Milestone 1 |
Added functionality to allow customers using on-premise installations of InRule products to use our centralized authentication provider. |
| FEATURE |
SEAL-1729 |
Update Flagship to target .NET Core SDK 3.0.100 |
The Linux-based Activation Utility now runs on .NET Core 3. |
| FEATURE |
SEAL-1732 |
REC needs a logout button |
Added a logout button to the InRule Rule Execution Console. |
| FEATURE |
SEAL-691 |
Update Documentation to show Stand Alone Catalog Manager is being Deprecated |
irCatalog Manager is being deprecated and will be removed in future versions. |
| FEATURE |
SFC-15 |
InRule for the Salesforce Platform - RuleHelper SaveEntity/SaveEntityCollection - do not include child entities when includeChildren parameter is false |
Fixed an issue when saving an entity or entity collection through the RuleHelper that would send child entity/collections as a part of the Salesforce payload even when includeChildren was set to false. |
| FEATURE |
SFC-17 |
InRule for the Salesforce Platform - Azure App Services Package for Azure Execution Service |
Created an Azure App Service model of the InRule Rule Execution Service. The Rule Execution Service can now be deployed as an Azure App Service rather than solely as an Azure Cloud Service, though Cloud Services support is maintained. For details on how to deploy and configure the Rule Execution Service as an Azure App Service, reference the updated deployment guide for InRule for Salesforce |
| FEATURE |
SFC-22 |
InRule for the Salesforce Platform - Upgrade DeveloperForce.Net package to latest (2.0.7) |
Upgraded the Salesforce solution to leverage the latest version of [DeveloperForce.Net|http://DeveloperForce.Net] (v2.0.7) |
| FEATURE |
SFC-25 |
InRule for the Salesforce Platform - Provide InRule 'Run Rules' button as a lightning web component |
Included a Run Rules Lightning Web Component as a part of the package for use in the Salesforce Lightning Experience. Run rules functionality is now supported in both the Lightning Experience and Classic View. |
| FEATURE |
SFC-33 |
InRule for the Salesforce Platform - irX Passthru connection for RuleHelper |
Implemented connection caching functionality for the RuleHelper. Users will no longer need to manually configure their irAuthor.config file with Salesforce connection information; all connection details will be cached and used when the user connects to their Salesforce environment through irAuthor. |
| FEATURE |
SFC-37 |
InRule for the Salesforce Platform - SalesforceRules RuleApp with samples to test execution integration and RuleHelper querying |
Updated the sample RuleApp provided with the Salesforce solution to provide better demonstration and examples of RuleHelper QueryEntity/QueryCollection functionality. |
| FEATURE |
SFC-40 |
InRule for the Salesforce Platform - Salesforce package deployment for InRule DecisionClient |
Overhauled installation process of the InRule Salesforce Solution Package. Manually uploading the package's associated Apex classes and dependent components is no longer necessary. Users will be provided with an installation link that will automatically install all components of the package. For a detailed walkthrough of this new installation process, refer to the updated InRule for Salesforce Deployment Guide. |
| FEATURE |
SFC-42 |
InRule for the Salesforce Platform - irX 'select all' option on schema entity field picker form |
Added a "Select All" button that allows users to select all fields or children for a given entity with a single button press. |
| FEATURE |
SFC-53 |
InRule for the Salesforce Platform - Add 'Log Level' setting to InRule config |
Created a new configuration setting in the InRule Custom Settings object in Salesforce that allows the user to set their desired logging level for the package. This new setting replaces the old method of configuring logging by directly editing the Javascript of the Run Rules button. |
| FEATURE |
SFC-57 |
InRule for the Salesforce Platform - Include Salesforce RuleHelper in the installer |
The Salesforce RuleHelper is now included as part of the irX installation process. |
| FEATURE |
SFC-60 |
InRule for the Salesforce Platform - Add 'RuleApp Name' setting to InRule config |
Added a new configuration option to the InRule Custom Settings object that allows the user to configure the RuleApp name that "Run Rules" buttons will execute against. This replaces the need for manually altering the Javascript of the Run Rules button for each RuleApp, as well as supporting the new Run Rules Lightning Web Component. |
| FEATURE |
SFC-62 |
InRule for the Salesforce Platform - Move rule execution service auth and url settings from custom setting to remote site settings |
Updated existing configuration options for the InRule Salesforce package, leveraging Salesforce's Named Credential functionality. Details on how to properly configure a Named Credential to properly work with the Rule Execution Service are provided in the updated InRule for Salesforce Deployment Guide. |
| FEATURE |
SFC-63 |
InRule for the Salesforce Platform - Display notifications returned from decision client |
The Run Rules button will now display fully detailed notifications and/or errors upon the execution of rules. These will be displayed in the form of a Salesforce toast notification on the page from where rules were executed in the Lightning Experience, and as a pop-up alert in Classic View. |
| FEATURE |
SFC-65 |
InRule for the Salesforce Platform - Implement Salesforce toasts for info, warning, error notification types |
Notifications, warnings and errors returned from the Rule Execution Service will now display as Salesforce Toasts of corresponding type when using the Lightning experience. |
| FEATURE |
SFC-66 |
InRule for the Salesforce Platform - Add RuleSet configuration to InRule Lightning Component |
Added a configuration field to the Run Rules Lightning Web Component. This field accepts a comma delimited list of RuleSet names. Adding multiple rule sets will create multiple Run Rules buttons for each defined RuleSet on the page. Leaving this field blank will leave only the singular "Run Rules" button, and this button will execute the Default RuleSet for the given entity. The Default RuleSet is defined as the entity's name + "DefaultRules". For example, if you are adding the Lightning component to the Account entity, the RuleSet name it will default to if this field is left blank is "AccountDefaultRules." |
| ISSUE |
DYN-260 |
InRule for Microsoft Dynamics 365 - Run Rules button drop-down display issue in Internet Explorer |
Resolved an issue that resulted in the Run Rules dropdown menu to not function properly in Internet Explorer. |
| ISSUE |
DYN-285 |
InRule for Microsoft Dynamics 365 - Dirty entity image on new entity - Javascript not detecting changes |
Resolved an issue that was causing rules to not properly execute on new, unsaved entities when DirtyEntityImage was set to true. |
| ISSUE |
DYN-286 |
InRule for Microsoft Dynamics 365 - Javascript error when handling option set field from Dynamics |
Resolved a bug that caused rules that updated entities with option set values to fail to execute. |
| ISSUE |
DYN-298 |
InRule for Microsoft Dynamics 365 - LoadMappedChildCollection method in RH Dynamics Driver throws error |
Fixed a bug with the LoadMappedChildCollection RuleHelper method that caused the method to return an unexpected error. |
| ISSUE |
DYN-332 |
InRule for Microsoft Dynamics 365 - RunRules Dropdown not populating in UCI in all cases |
Resolved a bug that resulted in the Run Rules dropdown list not properly populating in certain UCI Dynamics environments. |
| ISSUE |
DYN-340 |
InRule for Microsoft Dynamics 365 - Compatibility issue with Dynamics 8.2 due to inclusion of type 11 SVG |
Resolved an issue with 8.2 instances where importing the solution would prevent creation of any new web resources |
| ISSUE |
DYN-346 |
InRule for Microsoft Dynamics 365 - Error updating existing custom action step registrations |
Fixed an issue where step registrations with the custom action type could be created, but not updated |
| ISSUE |
DYN-353 |
InRule for Microsoft Dynamics 365 - Error running rules on entity create when entity has collections |
Fixed an issue in the execution service when running rules against an entity on create when that entity had collections imported |
| ISSUE |
SEAL-1342 |
BL Action's enabled checkbox doesn't do anything |
The "Enabled" checkbox on dialog boxes launched from the Language Rule editor do not affect whether the rule/action is enabled, so it has been removed. |
| ISSUE |
SEAL-1459 |
DB Installer Removes Data if Upgrading from Pre-EXE Instance |
Fixed a bug where the InRule.Catalog.Service.Database.exe installer would perform a new deployment and remove existing Catalog data if the installer was run against a catalog database that was created before using the DbUp library. This issue has been resolved and data will no longer be overwritten when running this installer, regardless of how the original catalog database was created. |
| ISSUE |
SEAL-1480 |
Language Rules do not have # indicator on Versions tab |
The Versions tool window tab for Language Rules now show a visual count indicator if it contains any items. |
| ISSUE |
SEAL-1490 |
Add a horizontal scrollbar for long rules in the regression tester for assertion tests |
A horizontal scrollbar was added to the Assertion Test window in irVerify. |
| ISSUE |
SEAL-1495 |
Loading JSON via irSDK or irServer causes auto-sequential RuleSets to execute when the Entity is created |
JSON deserialization will no longer execute rules while the rule engine is idle. |
| ISSUE |
SEAL-1502 |
irAuthor does not honor pinned items and window locations/sizing between sessions (close and open) |
In IrAuthor, windows that are pinned in custom configurations will now be remembered in between sessions. Custom windows locations will be remembered unless they are reset back to their default locations. Windows that can be pinned, resized and remembered are: Version, Version Settings, Description, Notes, Attributes, Cascade, and Links. |
| ISSUE |
SEAL-1511 |
Eval() use causes severe deterioration of irServer performance |
Eval() function performance improvement |
| ISSUE |
SEAL-1530 |
irAuthor will not validate rule application with Execute JavaScript Function |
irAuthor correctly identifies the platform when using the Execute JavaScript Function. |
| ISSUE |
SEAL-1582 |
Change description for Help Link on Portal to describe where it actually goes |
Updated verbiage for link. The link text previously said "The Getting Started Guide will walk you through key aspects of our Decision Platform." and was updated to say "To get started with Rule Authoring, see the InRule® Help file." |
| ISSUE |
SEAL-1807 |
irWord not supported. |
irWord is not supported in this release. It will be available again in a future release. |
| ISSUE |
SFC-1 |
InRule for the Salesforce Platform - Enforce Salesforce read-only fields are set to read-only in InRule entity schema |
Resolved a bug that resulted in Read-Only Salesforce fields imported to irAuthor not being properly flagged as Read Only. Read Only fields will now properly be imported as Read Only and can no longer be written to. |
| ISSUE |
SFC-12 |
InRule for the Salesforce Platform - Save entities with boolean fields with RuleHelper SaveEntity/SaveEntityCollection |
Resolved a bug in the RuleHelper that was preventing SaveEntity/SaveEntityCollection statements from properly executing if there was a boolean field on the entity to be saved. |
| ISSUE |
SFC-28 |
InRule for the Salesforce Platform - Deployment Guide Documentation Updates |
Overhauled the InRule for Salesforce deployment guide to include a detailed walkthrough of how to deploy out the new Rule Execution Service as an Azure App Service, how to proceed through the updated installation approach for the InRule Salesforce Package, and a number of appendices detailing lower-level configurations that are possible. |
| ISSUE |
SFC-46 |
InRule for the Salesforce Platform - Save entities with child entity collections with RuleHelper SaveEntity/SaveEntityCollection |
Resolved a bug that was preventing child entities/collections from properly saving when SaveEntity/SaveEntityCollection statements were run from the RuleHelper. |
| ISSUE |
SFC-49 |
InRule for the Salesforce Platform - Enable LoadChildren parameter for RuleHelper QueryEntity/Collection |
Resolved a bug that caused RuleHelper queries to break when the "LoadChildren" parameter was set to "true". |
| ISSUE |
SFC-61 |
InRule for the Salesforce Platform - Update DecisionClient to return error object in response |
The Run Rules button will now display fully detailed errors should executing rules fail for any reason. These will be displayed in the form of a Salesforce toast notification on the page from where rules were executed in the Lightning Experience, and as a pop-up alert in Classic View. |
Comments
0 comments
Article is closed for comments.