|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.
|Story||DYN-559||InRule for Microsoft Dynamics 365 - Update default view used in irVerify data loader||Default to selecting 'Active' view for loading entities in irVerify|
|Story||DYN-561||InRule for Microsoft Dynamics 365 - Check license during 'Test' connectivity in Configuration page||The connectivity test provided in the solution now validates the license for the execution service, in addition to the previous checks|
|Story||DYN-577||InRule for Microsoft Dynamics 365 - Surface Dynamics configuration through the InRule SaaS Portal||Added management and display for Dynamics configuration to the InRule SaaS Portal. This information is displayed in the existing Configuration page, and shows settings required to configure the InRule for Dynamics solution, such as the relay URL. Customers can also configure the authentication information required to connect to their Dynamics instance, either by providing service account credentials or using the InRule S2S application. Further information can be found in the 'InRule SaaS Portal Configuration' section of the deployment guide.|
|Story||DYN-579||InRule for Microsoft Dynamics 365 - Improve display of deprecated fields and entities in irX schema management||Some Microsoft entities and fields were updated by Microsoft to have \[Deprecated] or (Deprecated) added to the beginning of their names. Sorting has been modified to float these to the bottom of lists in irX schema management|
|Story||DYN-588||InRule for Microsoft Dynamics 365 - Add SaaS config page to InRule Dynamics Solution||Added a new page to the InRule solution and sitemap to aid configuration for SaaS setups. This page allows you to grant the required consent to the InRule Azure AD application, and creates the associated Application User for you|
|Story||DYN-594||InRule for Microsoft Dynamics 365 - Update Application Insights resource creation via ARM Template||Deprecate createOrUpdateAppInsightsResource parameter in ARM template for execution service deployment. Refer to Deployment Guide for directions to deploy Application Insights resources|
|Story||SEAL-3180||Weak Password complexity - Findings from Pen testing||You may require that new passwords meet a complexity rule when they are being assigned to users using the Catalog Manager website.
See the Security section of the InRule Installation Guide to learn how to activate this optional feature.
|Story||SEAL-3181||Lack of Logon Brute Force -Findings from Pen testing||You may protect against brute force login by deactivating any account that experiences too many unsuccessful logins in too short a time frame.
See the Security section of the InRule Installation Guide to learn how to activate and configure this optional feature.
|Story||SEAL-3182||Lack of Server-side logout - Finding from Pen testing||See release note for SEAL-3187|
|Story||SEAL-3183||Lack of CSRF Protection - Finding from Pen testing||See release note for SEAL-3187|
|Story||SEAL-3187||HTTPSECURITY HEADERS &CACHE CONTROL HEADERS ARE LACKING||Made multiple security enhancements to the function of the Catalog Manager website, the SaaS Portal, and the Rule Execution Console.|
|Story||SEAL-3331||Flagship: Update Integration step to update Flagship Installer with Sigao help documents artifacts||Fixed an issue that was causing the help documentation for the Salesforce and Dynamics extensions to be outdated.|
|Story||SEAL-3513||Remove version number and copyright from splash screen||The version number and copyright have been removed from the Splash Screen. The information is available on the bottom right-hand corner of the irAuthor main page.|
|Story||SFC-120||InRule for the Salesforce Platform - irX data loading performance improvements||Unified the irX and execution service entity data loading. This allows for irX to leverage the improvements made in the execution service's data loading, improving performance considerably.|
|Story||SFC-169||InRule for the Salesforce Platform - Handle errors coming from Salesforce in run rules button||Add additional error handling to the Run Rules button for errors thrown by the Salesforce Platform, such as 'Storage Limit Exceeded', and display these errors to the user.|
|Story||SFC-193||InRule for the Salesforce Platform - Support saving multiple levels of new entities||Rule execution capabilities have been expanded to support creating multiple levels of new entities within rules. For example, creating a new entity, then adding additional new entities to a collection on the original entity. InRule for Salesforce now processes these changes in the correct order to ensure all entities are saved correctly.|
|Story||SFC-198||InRule for the Salesforce Platform - Check license during 'Test' connectivity in Configuration page||The 'Test Connectivity' button on the InRule Configuration Lightning page now includes a license health check to ensure the Salesforce execution service has a valid license associated with it. If the license is missing or invalid, an appropriate error will be displayed.|
|Story||SFC-200||InRule for the Salesforce Platform - Create default custom setting object as part of install||The custom settings object needed for the InRule for Salesforce App is now created as a part of the app installation process. Default values are set if no object exists, but these can be configured after install as usual|
|Story||SFC-214||InRule for the Salesforce Platform - Resolve issue with composite batch api limit||Frequent loading of large entity trees would lead to hitting a specific API limit for the Connect/composite batch api at 2000 request per hour. The entity loading has been modified to no longer use this API, so the only limit hit will be the standard daily limit|
|Story||SFC-215||InRule for the Salesforce Platform - Update salesforce API version to Summer 21||InRule for Salesforce compatibility with the Summer 2021 release has been verified. API versions in the InRule Salesforce package, execution service, and irX have been updated to v52.0.|
|Story||SFC-218||InRule for the Salesforce Platform - Surface Salesforce configuration through the InRule SaaS Portal||Added management and display for Salesforce configuration to the InRule SaaS Portal. This information is displayed in the existing Configuration page, and shows settings required to configure the InRule for Salesforce package, such as the execution service URL. Customers can also configure the authentication information required to connect to their Salesforce instance by providing a service account and the required connected app info. Further information can be found in the 'InRule SaaS Portal Configuration' section of the deployment guide.|
|Defect||DYN-563||InRule for Microsoft Dynamics 365 - Minor irX Advanced login dialog UI fixes||Fixed some UI issues that would cause blocking windows or errors when using various irX popups|
|Defect||DYN-605||InRule for Microsoft Dynamics 365 - Runtime error when disabling auto-load for lookups||Resolved issue when disabling Auto Load but not on Auto Save that resulted in persistence error|
|Defect||DYN-607||InRule for Microsoft Dynamics 365 - Add better error handling for malformed connection strings||Provide a more helpful error when a malformed connection string is supplied to the execution service|
|Defect||SEAL-3511||irJS: ExecuteMemberRuleSet, CopyCollection, and ForEach actions that use a filter fail to execute remaining rules in rule set||Resolved a bug in the Distribution Service. The ExecuteMemberRuleSet, CopyCollection, and ForEach actions that use a filter will now execute the remaining rules in a rule set.|
|Defect||SEAL-3741||Support Cutover: Hide the support forums and Support website link in irAuthor||Support Forums and Support Website link have been removed from the About and the Contact section in irAuthor. InRule help documentation can be accessed using the help icon or under 'docs' in your InRule installation folder.|
|Defect||SFC-186||InRule for the Salesforce Platform - irX Cancel Login Error||Resolved a bug that caused an authentication error to be thrown in scenarios where users cancelled a login attempt.|
|Defect||SFC-191||InRule for the Salesforce Platform - Allow blank api token||The API Security token is now no longer required to be configured on the Salesforce execution service to support use cases where trusted user profiles and IP ranges have been established, as such users do not have API security tokens. User accounts that are not associated with a trusted profile or IP range must still configure a token value to authenticate to Salesforce during rule execution.|
|Defect||SFC-206||InRule for the Salesforce Platform - Disabling auto-load for lookups causes persistence error||Resolved a bug that caused disabling auto-load without disabling auto-save for a lookup field on an entity to send back a change to clear the field, even when no changes were made|
v5.7.2 Release Notes
Was this article helpful?0 out of 0 found this helpful
Please sign in to leave a comment.