v8.3.3337.0903
- 19 Oct 2018
- 1 Minute to read
- Print
- DarkLight
- PDF
v8.3.3337.0903
- Updated on 19 Oct 2018
- 1 Minute to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Release Date: 10 March 2017
This is a minor patch release which resolves the below issues.
Bug Fixes
| Reported Issue | Comments/Fix Provided | Section in BizTalk360 |
|---|---|---|
| Unable to access Agreement details from Parties & Agreements | Post V8.3 upgrade, the users were unable to access the AS2/X12 agreements under Parties & Agreements section. This issue is fixed in this patch release and the users can access the AS2/X12 agreements as expected. | Operations > EDI > Parties and Agreements |
| BAM data monitoring filter restricted | When configuring BAM Data monitoring, the filter option under "Set Data Filter" was restricted to "Is equal to". The user was unable to set any other filter condition. This issue is fixed and works as expected. The user can set all the available filters in BAM Data monitoring. | Monitoring > Data Monitoring |
| Issue in "Next Run Time" option in BAM data monitoring | When the user tries to change the BAM data monitoring from weekly to daily or vise-verse, the "Next Run Time" option doesn't work as expected in the V8.3 release. This issue is fixed and the user can now switch between the daily and weekly views without affecting the "Next Run Time". | Monitoring > Data Monitoring |
| MSMQ take long time to load and save | We observed the Queues taking a long time to load and save. The timeout value for each message in an active queue is now optimized to resolve this issue. Now the MSMQ screen loads faster than before. | Monitoring > Queues Monitoring |
Was this article helpful?