- Updated On 19 Oct 2018
- 2 Minutes To Read
Release Date: 21 August 2017
This is a minor patch release which resolves the below issues.
|Reported Issue||Comments/Fix Provided||Section in BizTalk360|
|Installer failed to upgrade when ESB is configured in more than one environment||When we have two or more environments configured for ESB, the installer failed to upgrade to v8.5. This issue is fixed and the upgrade will happen seamlessly.||Version Upgrade|
|Exception in Host Throttling monitoring||When the user changes the Date & Time format as "DD-MM-YYYY" in the user profile, an exception is shown in host throttling monitoring section. This issue is fixed and the exception will not be displayed when the user changes the date & time format.||Monitoring -> BizTalk Environment-> Host Throttling|
|Validation symbol not displaying while configuring ESB Exception||While validating ESB exception, for the OnRamp URL the validation symbol(Tick mark) is not appearing as expected. This issue is fixed.||Settings -> ESB Portal Settings|
|Service instance details are not being shown in the email alert||When you enable the "Send Instance Detail In Notification" in the Message Box data monitoring, service instance details are not displayed in the email alert. This issue is fixed and service instance details will be shown in the email alert.||Monitoring -> Data monitoring ->Message Box Data Monitor|
|Group by query result was not displayed for Suspended service instances||In Message Box (Queries), When the error description content has 1024 character for the suspended service instances, group by query result was not displayed. This issue is fixed and query result will be displayed when the content is up to 1024.||Operations -> Data Access -> Message Box(Queries)|
|Exception in alarm creation process||When you give a special character like "&" in the alarm description, an exception is displayed in the create alert monitoring sub service. This issue is fixed and when the user gives special characters like ~!@#$%^&*()_+||":?,./;'][` the email alert will be triggered and the exception will not be displayed.||Monitoring -> Manage Alarms|
|HTML code provided to link text is not reflecting in the email alert||In alarm description, when an HTML code is provided to a hyperlink for any text then the text will not be reflected in the generated email alert (eg: Click for wiki page) Instead user need to do the direct link. This issue is fixed and when the direct HTML code is provided, that gets reflected in the generated email alert.||Monitoring -> Manage Alarms|
|When FTP and SFTP locations are configured with the invalid location, the configuration became orphaned in BizTalk Server 2013 R2 version.||When the FTP and SFTP monitoring are configured with the invalid location, the configuration became orphaned with a double entry in the grid view. This issue is fixed and configuration will become orphaned without duplicate entry.
Note: After the migration, existing orphaned configuration needs to be removed in order to monitor the FTP & SFTP locations.
|Monitoring -> File Location|
|Enhancement||Comments/Fix Provided||Section in BizTalk360|
|Custom Cache Implementation||To improve the response time for few of the REST calls we have enabled Active Directory Cache. By default, this option will be disabled. If you have complex NT Group setup, Active directory cache can be enabled to improve the performance.||Settings -> System Settings|
Was This Article Helpful?