| Schema view not aligned properly | In Version 7.2, we added the ability to view the schema in a nice tree view editor with the capability to expand/collapse the nodes. For few applications, the schema view was not displaying as expected. This issue is now fixed and the schema view displays as expected for all the applications. | Search Artifacts > Application > Schema View |
| Contains operator not working as expected | In few sections, executing the query with the ‘URI’ filter using the ‘Contains’ operator was not working as expected and did not return the correct results. This issue has been fixed and now when the user executes the query with the ‘Contains’ operator, the system displays the expected results. | Message Box (Queries)Graphical Flow (Tracking) |
| Date time stamp to be consistent in the Grid and Select Query area | In few sections, the date-time stamp was displayed in mm:dd:yyyy format in the grid while in the Select Query control, it was displayed in m/dd/yyyy format. This inconsistency has been fixed in this release and the date-time stamp will display in dd-MM-yyyy HH:mm:ss format. In addition, the tooltip for date-time picker has been removed across the board. | Message Box (Queries)Graphical Flow (Tracking)ESB Exceptions Advanced Event Viewer |
| Modal window goes out of bounds in Internet Explorer 9 browser | In IE 9, the modal window for the properties was not within the page boundary limits. Upon analysis, it was found that the issue occurred because we had updated one of the libraries in the system. This caused IE 9 to overshoot the boundary limits. This issue is now fixed and the CSS is structured to handle this. The property window displays within the page boundary limits in IE 9 and other browsers. | Search Artifacts (and associated sections)Applications (and associated sections)Message Box (Queries) Graphical Flow (Tracking) ESB Exceptions Advanced Event Viewer Settings |
| Spelling errors | The spelling errors in the application have been fixed across the board | Across the entire application |
| Service returns “Retrieving the COM class factory for component with CLSID {…} failed” error message | This issue happens when you have BizTalk360 configured to run as a specific user. When you log off from the application, the application cannot read the registry keys in the user profile as the user profile gets unloaded. This is an inbuilt Windows functionality. Therefore, the system returns the “Retrieving the COM class factory for component with CLSID {…} failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA)” error. This issue has been fixed by identifying a workaround for this problem. To avoid the COM class factory error, you need to disable the user profile getting unloaded when you log off from the application. Enable the policy setting ‘Do not forcefully unload the user registry at user logoff”. By doing this, Windows does not unload the registry and waits until it confirms no other processes are using the user registry. | Message Box (Queries) |
| GroupBy filtering remains even after changing the query | In Message Box (Queries), when the user builds a query expression with the Group Results By filter, the system displays the results. But when the user immediately changes the query to ‘Messages’, the system does not remove the Group Results By filter information and it remains on the screen. This issue has been fixed and now when the user clicks on ‘Messages’ after creating a query expression with Group Result By filter, the system removes the information related to the previous query expression. | Message Box (Queries) |
| Unable to edit query after clicking on it for the second time | The ‘Edit Query’ functionality was not working as expected due to the Query text box formatting issue. This issue has been fixed and now the user can click on the edit query button multiple times to edit the predefined query information. | Custom SQL Queries |
| An issue with starting and stopping monitoring services | On few occasions, the starting and stopping of monitoring services did not happen correctly. This was because of the timezone differences of the server and how the start and stop times were being handled. This issue has been fixed and now the starting and stopping of monitoring services will happen correctly for servers located in different time zones. | Settings > BizTalk360 Health Status |
| UI validation issues when entering the event log values | In the ‘Event Log Alert – Threshold Violation Settings‘, the system did not accept the value as 0 for errors, warnings, and information events. Similarly, there was no validation being done for the values that can be entered for the fields. This issue has been fixed and proper validations are in place for the errors, warnings, and information events fields in the ‘Event Log Alert – Threshold Violation Settings‘ section. Also, in addition, a validation check has been added for the ‘Logged in Last’ field where the system can accept only 2 minutes or later. | Monitoring and Notification > BizTalk Servers > Event Logs > Event Log Alert – Threshold Violation Settings |
| Download messages via Email – Validations | In Message Box (Queries), the user has the ability to save the query results in PDF and send the result via email. But proper validations were not in place when the user entered special characters/invalid email address and so on. This issue has been fixed and validations have been added in the system that will check the email address entered by the user. | Message Box (Queries) |
| User access policy issue when viewing Message Details | In the user access policy section under Settings, when the ‘Message Content/Context’ check box is not selected, the system still displayed the option to query on the messages and view the message properties for Message Box (Queries). Similarly, for the Graphical Flow (Tracking) section, despite the ‘Message Content/Context’ not being selected, the system displayed the Message Context properties. This issue has been fixed and now when the user access policy is set for ‘Message Content/Context’, the user will not see the option to be able to query on messages or download the messages, and also will not be able to view the Message Content and Content Properties information. | Message Box (Queries) |
| Setting NT Services to ‘Do Not Monitor’ status displays wrong status information | In the Monitoring and Dashboard section, when all the NT Services were set to ‘Do not monitor’, the system displayed the wrong status in the dashboard. This issue has been fixed and now setting the NT Services to Do not monitor, the system will remove the configuration information and does not display the information in the monitoring dashboard. | Monitoring and Notifications > SQL Servers > NT Services |
| Service property not displaying as expected for Normal Users | In the Graphical Flow (Tracking) section, when the user (non-Super user) clicks on the Properties icon, the service properties information was displayed only for the first time. Subsequently, when the user clicked the Property icon, the service information was not displayed. This issue has been fixed and now the service property information will be available for non-superusers whenever they click on the Properties icon. | Graphical Flow (Tracking) |
| The application list did not get displayed completely for Non-Super users | When only a few applications were permitted for non-superusers under user access policy, not all the permitted applications were visible and only the first few items were displayed. This issue has been resolved and now all the selected applications will be listed for non-superusers. | Applications Search Artifacts |
| Service property not displaying as expected for Normal Users | In the Graphical Flow (Tracking) section, when the user (non-Super user) clicks on the Properties icon, the service properties information was displayed only for the first time. Subsequently, when the user clicked the Property icon, the service information was not displayed. This issue has been fixed and now the service property information will be available for non-superusers whenever they click on the Properties icon. | Graphical Flow (Tracking) |
| Time selection to stop alerts for maintenance | In the Stop alerts for maintenance section, the user was unable to set a stop alert for maintenance to an immediate time. This issue has been fixed and now by default if the maintenance is not present for the selected environment, the date-time box will automatically be populated with the current date-time. The time in the drop-down will start from the next immediate 30-minute window. For e.g., if your maintenance time when you want to execute the process monitoring is 6/19/2014 3:04 PM, the date time picker drop-down will display the date from June 19, and the time range will start at 3:00 PM. In addition, we have also fixed an issue where the date and time did not get displayed for an active maintenance alert. You will now be able to see the current time in the field (although it will be grayed out during an active maintenance period). | Settings > Monitoring and Notifications > Stop Alerts to maintenance |
| Validation issues | In the HP Operations Manager section under Settings, Save and Verify buttons are not enabled after a validation error message appears on the screen, and when the user wants to verify the information once again. This issue has been fixed and now when then there is a validation error message (when no values are entered and a user clicks Verify) and then the user tries to enter some text and save the values, the Save and Verify buttons are enabled. The validation checks were also not in place for Disk Configuration sections in BizTalk server and SQL server section. When the user did not enter any values and saved the setting, no validation error message is presented and the system returned an exception error message. This issue is fixed and proper validations are now in place to verify whether the fields contain the valid inputs. On the Manage Alarms page, when a duplicate alarm name was provided and > icon is clicked, the application displayed an error/exception message. But when the duplicate name was replaced with a different name, the error/exception message was still visible. This issue has been fixed and the exception message will no longer be visible once the alarm name is modified. | Settings > Monitoring and Notifications > HP Operation Manager Settings > Monitoring and Notifications > BizTalk Servers and SQL Servers Settings > Create some alarms and map artifacts > New Alarm |
| Refresh icon (Page Refresh and grid refresh) issues | In the Message Box (Queries) section, when the user clicks on the Refresh icon without executing a query, the query results for the item under the ‘Select Query’ drop-down were displayed by default. This issue has been fixed and clicking the refresh icon does not load the information for the item under the ‘Select Query’ drop-down. On the Settings page, when a user clicked on the ‘Refresh’ icon at the top of the page, the icon jumped to the next line. Once the refresh completes, the icon was restored back to its original position. We have fixed this issue and the icon is displayed in the same line when the page is being refreshed. In the ‘Governance/Audit-By Host Instance’ page, the Refresh icon was not as consistent as in the other areas of the application. This issue has been fixed and the Refresh icon look has been made consistent across the entire application. | Message Box (Queries)Settings > Governance/Audit – By Host Instance |
| For normal users, Group Results By arrangement is misleading | In the Message Box (Queries) section, when a user executes the query based on the ‘Group Results By’ filter, the column arrangement (application name and count) was swapped for super users and normal users. This issue is fixed and both super and normal users will see the same column arrangement for the Group Results By filter. In addition, Service Class filtering was not happening properly after the filtered result is selected in the Message Box (Queries) section. This was happening when a filter (GroupBy Is Equal to Service Class) was added. This issue has also been fixed and now users will not see the service class filtering errors. | Message Box (Queries) |
| Unable to close the pop-up window on few screens | The users were unable to close the pop-up windows on certain screens (Schema View Properties). This issue is fixed across the board where this problem occurred and now clicking the close link closed the pop-up windows. | Schema View Properties, Message Box Service Properties, Applications Schema Properties |
| Clicking the ‘Select All’ check box in the Firefox browser navigated the user back to the dashboard page | When the user clicked the ‘Select All’ check box filter option, the application navigated back to the dashboard page. This issue has been fixed and now when the ‘Select All’ filter is selected, the records in the grid will be selected. | Across the entire application |
| Time latency with expandable/shrinkable feature in the properties window | Across the application, the properties window had the capability to be expanded/shrunk back to the original size. However, when the expanded area was being shrunk, it caused a time delay to complete the operation. This issue has been fixed and now the expandable/shrinkable option feature for the properties window has been removed. The text area will automatically adjust according to the information. | Across the entire application |
| Unable to view the properties of unenlisted items | In few areas of the application, users were unable to view the properties of the unenlisted items. This issue was due to an undefined property error that was occurring when the user tried to view the properties. This issue is fixed and now when the properties icon is clicked for unenlisted items, the user is able to see the properties information as a pop-up window. | Application Search Artifacts |
| Truncate long artifact names to fit the size of the window and display “…” with tooltip | In few areas of the application, few artifacts had very long names that extended beyond the property window text area, while few artifacts did not display the name in the properties window. This issue is fixed and now the artifact name is truncated to be displayed within the property window text area. The remaining text is replaced with “…”. In addition, we have added tooltips to display information. In few other sections, when mouse over happens, we have expanded the tooltip area to display the tooltip message completely. | Applications (Property window sections) |
| Validation while adding new SQL Server name | On the Settings page, when the user has the ability to add a new SQL server, there was no validation in place and the application allowed the user to enter junk characters. This created issues in the monitoring dashboard where SQL servers were not being listed in the monitoring graph even though monitoring was enabled for the SQL server artifacts. This issue is now fixed and validations are in place to not allow the users to enter any junk characters. While addressing the fix, it was also noticed that the NT service monitoring for SQL servers was not returning the expected value when all NT Services were set to the ‘Do not monitor’ state. This issue has been fixed and when all the NT Services are set to ‘Do not monitor’ state, the configuration is removed and the monitoring graph will not display the NT services leaf node. | Settings > Monitoring and Notifications > SQL Servers for Monitoring |
| Duplicate error messages | While trying to start the host instances, if the operation failed, the application displayed an error message “Failed to start the BizTalk Host Instance …”. But the error message was duplicated on the page. This issue is now fixed and only one error message will be seen on the page if the host instance fails to start as expected. | Platform Settings |
| “Test Connection” button not working in Manage Environments | When the test connection button was clicked, the corresponding action (of validating the license and environment information) did not happen. This issue is fixed and now when the ‘Test Connection’ button is clicked, the system will validate the information in the form and display a confirmation message (in the background) as “Environment updated successfully”. | Settings > Environments/Licenses |
| No warning message when the ‘Message Content’ data was too large to handle | When the message content section had over 50000 characters, there was no warning message displayed and the complete message content was not visible. This issue is fixed and the application will display a warning message when the message content section has more than 50000 characters. | Message Box (Queries) > Message ContentGraphical Flow (Tracking) > Tracked Message EventsGraphical Flow (Tracking) > Tracked Service Instance |