| Type |
Case ID |
Summary |
Description |
| FEATURE |
DYN-182 |
InRule for Microsoft Dynamics 365 - Add Max Plugin Depth Check configuration setting |
Added configuration setting to increase the maximum plugin depth check, up to a max of 50. Increasing the max plugin depth check to at least 2 allows for the execution of rules via Custom Workflows. |
| FEATURE |
DYN-185 |
InRule for Microsoft Dynamics 365 - Dynamics Solution Getting Started page and navigation |
Added a new "InRule" section to the sitemap under the Settings tab. The InRule section contains a new "Getting Started" page that provides a high level overview of the Rule Services Solution, installation of its dependencies, and its usage. Additionally, it provides a direct link to the Rules Configuration page that formerly could only be accessed through Rule Services solution menu. |
| FEATURE |
DYN-204 |
InRule for Microsoft Dynamics 365 - Publish InRule Dynamics 365 Solution to Microsoft AppSource |
InRule Dynamics 365 Solution is now available on Microsoft's AppSource as an alternative installation method, as opposed to the traditional PowerShell deployment method. It is worth noting that only the Dynamics solution can be deployed through Microsoft's AppSource. All resource dependencies, including the Rule Execution AppService, the Azure Service Bus, and the Rules Catalog must still be deployed as defined in the InRule for Dynamics 365 Deployment Guide. |
| FEATURE |
DYN-210 |
InRule for Microsoft Dynamics 365 - Improve on-prem rule service response error handling |
Added improved error-handling for on-prem installations to provide more meaningful exceptions in the event of a 404 or 500 response from the Rule Execution Service. |
| FEATURE |
DYN-213 |
InRule for Microsoft Dynamics 365 - Configuration to map Run Rules button to specified Entity and RuleSet |
The InRule custom action now supports entity-specific configuration, and can be configured on the solution configuration page. This includes, but is not limited to, disabling the RunRules button for certain entity types and not others, or setting separate max plugin depth checks for different entity types. The selected configuration is applied whether the custom action is invoked through the 'Run Rules' button, or invoked through some other method such as a rest call. If an entity type doesn't have a specific configuration associated with it, it will use the Default Rule Configuration. |
| FEATURE |
DYN-220 |
InRule for Microsoft Dynamics 365 - Ability to select Ruleset from a drop-down list on the Entity form Run Rules button |
The Run Rules button will now display a drop-down list of available rulesets specified in RuleSet List configuration setting in the Rules Configuration form. By associating Rules Configuration records to specific entities via the Custom Action configuration, a user can now control the list of rule sets available on an entity by entity basis. |
| FEATURE |
DYN-223 |
InRule for Microsoft Dynamics 365 - Add Return Full Entity Image configuration setting to return the complete EntityImage in rule response |
Added a configuration option to only return fields updated via rule execution, rather than the entire entity image. The default setting remains to return the entire entity image, but this can now be changed through the Rules Configuration interface. |
| FEATURE |
DYN-229 |
InRule for Microsoft Dynamics 365 - Add RuleSet List configuration setting to manage list of rule sets available for Run Rules button |
Added a new configuration field that allows for the Run Rules button to be "scoped" to multiple different rule sets. By default, the Run Rules button is scoped to only run the default rule set that is specified in the configuration file. With this RuleSet List field, you have the option to add a comma separated list of rule sets that may be selected. When this is populated, the Run Rules Button will have a dropdown menu added to allow you to select the rule set when running the rule. |
| FEATURE |
DYN-40 |
InRule for Microsoft Dynamics 365 - RuleHelper to leverage cached connection/configuration from host process |
Added functionality to the RuleHelper to use Dynamics connection information from the environment specified in the Dynamics ribbon in irAuthor. Instead of configuring connection strings in the irAuthor config xml file to run RuleHelper queries, queries will now execute against the environment specified when testing from the Dynamics ribbon in irAuthor. |
| FEATURE |
DYN-48 |
InRule for Microsoft Dynamics 365 - Add support for Multi-select option sets |
Added support for Dynamics MultiSelect Option Set fields to irAuthor. These field types can now be added through irX and are implemented as a Complex collection data type in irAuthor. NOTE: This enhancement requires that the Dynamics Integration Framework is now only compatible with Dynamics v9.0 for both online and on-prem. To deploy to a v8.2 Dynamics environment, contact InRule support at support@inrule.com for a compatible build. |
| FEATURE |
DYN-50 |
InRule for Microsoft Dynamics 365 - Configuration to manage InRule plugin step registration (eliminating reliance on plugin registration tool) |
Step registrations can now be managed within Dynamics itself, instead of having to use the Plugin Registration tool. The solution configuration page supports creating and upating steps registrations for the InRule plugin with Create, Update and InRule custom action messages. |
| FEATURE |
DYN-59 |
InRule for Microsoft Dynamics 365 - Allow RuleHelper query filters to reference fields at lower levels |
Added functionality to the RuleHelper that allows for filter expressions with queries against related entities. Querying against related entities requires that all entities queried in the relationship chain be imported into irAuthor. The queried fields on each of the queried entities do not necessarily need to be imported, but if they are not, the entire Dynamics schema field name must be used, rather than their irAuthor aliases. Refer to Appendix D of the Deployment Guide for more information. |
| FEATURE |
DYN-69 |
InRule for Microsoft Dynamics 365 - Add Rule Execution Log configuration setting |
A new setting has been added to to enable InRule execution log tracing. When enabled, the InRule execution log will be passed back from the rule execution service and logged to the plugin trace |
| FEATURE |
DYN-78 |
InRule for Microsoft Dynamics 365 - New Rules Execution Workflow Activity |
Added a Rules Execution Workflow Activity to allow for the execution of the InRule Custom Action through Dynamics workflows. Workflows can now process rules and will return the results as output parameters. |
| FEATURE |
SEAL-1026 |
Validate support for SQL Server 2017 |
SQL Server 2017 is supported for irCatalog. |
| FEATURE |
SEAL-1285 |
Update irCatalog and irCatalog Manager Encryption to AES Encryption |
Updated the encryption protocol used when communicating with irCatalog and credentials stored with irCatalogManager. |
| FEATURE |
SEAL-1322 |
Update irWord to support TLS 1.2 |
Added support for TLS 1.2 in irWord when connecting to irCatalog. |
| FEATURE |
SEAL-1384 |
WCF BasicHttpBinding and endpoint should be included in irCatalog config by default |
WCF BasicHttpBinding and endpoint are now included in irCatalog config by default |
| FEATURE |
SEAL-1427 |
Include Dynamics RuleHelper in the installer |
RuleHelper assemblies are now automatically installed into the EndPointAssemblies folder of irAuthor when installing irX for Microsoft Dynamics CRM. |
| FEATURE |
SEAL-1437 |
IEnumerable Support for bound entity state objects |
Added support for importing .NET Assembly Schemas containing collections that implement IEnumerable<T> or ICollection<T>. Also added runtime object entity state support for collections that implement IEnumerable<T> or ICollection<T>. |
| FEATURE |
SEAL-1440 |
Add Template Analyzer to Determine Business Language Template Usage |
Added a new SDK feature for getting the list of templates consumed by a business language rule. |
| FEATURE |
SEAL-388 |
Deprecate and Remove irStudio |
As irStudio was not a priority for our customers, we have discontinued it moving forward. |
| ISSUE |
DYN-183 |
InRule for Microsoft Dynamics 365 - On-Prem Solution - Configuration screen does not show Active Rule Configurations |
Resolved an error that was resulting in the Active Rule Configuration entities not appearing on the Rules Configuration page in on-prem installations with multiple organizations. Active Rule Configurations should now properly appear. |
| ISSUE |
DYN-230 |
InRule for Microsoft Dynamics 365 - Error message running rules with changed entity lookup reference (unsaved) and UseDirtyEntity to true |
Fixed a bug that resulted in an error being generated if the user attempted to run rules via Custom Action or through Javascript on a dirty entity when the entity reference had been updated. |
| ISSUE |
SEAL-1332 |
Fix Static Cache Memory Leak in Business Language |
Resolved a bug in Business Language that could result in excessive memory usage. |
| ISSUE |
SEAL-1349 |
Allow logging of REST call failures from rule applications to be disabled |
By default, Execute REST Service Action will no longer log request and response bodies to a text file when the REST endpoint returns a 500 response code. To enable this behavior enable Debug logging via the applications configuration file. For more information on how to set InRule logging levels, please refer to the "InRule Logging Config File Settings" section of the Developer Help file, located at C:\Program Files (x86)\InRule\doc\InRuleSdkHelp.chm. |
| ISSUE |
SEAL-1443 |
Exception Occurs When .NET Core Uses RuleCatalogConnection On A Catalog With AD Authentication |
Resolved a bug that caused an unhandled exception when a .NET Core application attempted to communicate with irCatalog when configured to use Active Directory authentication. |
| ISSUE |
SEAL-1448 |
Unhandled exception in Installer when upgrading irCatalog already configured with .NET Core endpoint |
Resolved a bug that caused an unhandled exception when upgrading irCatalog from a prior version that had mutiple WCF endpoints defined in its configuration file (i.e. web.config or RepositoryWindowsService.exe.config). If you have configured irCatalog to use HTTPS and want to use the newly added .NET Core endpoint (the same url as the standard irCatalog Service url with "/core" appended to the end), you may need to manually update your irCatalog configuration file. If you have HTTPS configured, locate "wsHttpBinding" and "basicHttpBinding" in the configuration file, and make sure both have <security> element with the setting "mode" set to "Transport". If those settings are set to "None", then communication over HTTPS will not work. |
| ISSUE |
SEAL-1450 |
irCatalog Manager gives "Length of the data to decrypt is invalid" error |
Resolved a bug that caused a "Length of the data to descrypt is invalid" error to be given in irCatalog Manager when credentials are stored in irCatalog Manager using AES encryption. |
Comments
0 comments
Article is closed for comments.