HotFix - Manitou 2.1.x

Articles

HotFix - Manitou 2.1.x - 02-02-2023: Fix for issue with ASAP to PSAP Send button not active to send update messages (Bugs 33046) (v2.1.30)
Issue Description: In the Manitou Web Client, when sending additional information using the asap-to-psap process the message comm-center appears but the 'send' button is disabled. This has been fixed along with what happens after 'send' is sele...
01-20-2023: Fix for Dashboard Customization and Missing Reports/Report Criteria in Turkish Windows Region (Bugs 31173 and 32278) (v2.1.36)
Issue Description: On Manitou installations on Turkish servers (Windows installation w/region set to Turkish), Dashboard Customization wasn't saving or displaying and some Reports were missing entirely or missing Options or Advanced fields. Thi...
Development - 5-26-2021: BoldNetWeb unable to remove on-test using quick remove function (v2.1.25)
Issue Description: When using the quick remove function, it is pulling the date in the wrong format due to their date format being DD/MM/YYYY. Repro-Steps: Add an on test using the quick function for 1 hour. Delete the On test...
Development - 5-11-2021: Webservices SOAP API data error from CustomerService.svc (v2.1.21)
Issue Description: The following error can occur when attempting to get customer logs from Manitou, that appears intermittently in certain customers without any indication on what could be causing the problem. Error message: "An error...
Development - 4-30-2021: Queue Rollup showing high pri alarm as suspended (when not) if low pri is suspended on same customer (v2.1.25)
Issue Description: In MWC and OWS, in the Alarm Queue (Summary by Master Customer style (aka. Queue Rollup)) a higher priority alarm was set as suspended if a lower priority previous alarm had been suspended. We made a change so that if any exi...
Development - 3-12-2021: Remove On-Test issue (v2.1.22/v2.1.23/v2.1.24)
Issue Description: In MWC and BoldNet Web, attempting to delete an On-Test entry would result in failure if any other On-Test entries exist for a System Account that has no Address information. Solution: We made the necessary changes ...
Development - 2-11-2021: Pulling account over from SedonaOffice in VB (v2.1.20/v2.1.21)
Issue Description: As part of the integration with SedonaOffice, it is possible to first create the account in Sedona, then begin the account creation process in Manitou but search and find that existing account in Sedona. Manitou will pull the...
Development - 1-20-2021: Orphan signals hitting wrong account (v2.1.21/v2.1.22)
Issue Description: When a signal comes into Manitou that does not directly map to a known account, it tries to then find a dealer with an RLP/TXID range that includes this signal. If that dealer has a system account, it sends it there. If not, ...
Development - 1-5-2021: Fix for Stealth Viewer Runtime Error 35773 (v2.1.xx)
Description of Issue: Getting runtime error when launching Stealth Viewer and History lookup values will not go past 12/31/2020 Runtime Error 35773 A Date was specified that does not fall within the MinDate MaxDate properties. Fixes: When do...
Development - 12-2-2020: MWC Alarm queue not refreshing for unique case (v2.1.21)
Issue Description: Damar has a strange case that appears to only be happening for remote dealer restricted users. IF they get a "reconnecting to AppServer" spinner, and they have low queue activity, they get into a strange state where the alarm...
Development - 12-2-2020: Alarm remaining allocated when browser refreshed (v2.1.18)
Issue Description: Interface found that if they refresh (or close the browser and quickly login with the same user), if the same session is given to the user, the previous alarm will remain allocated to them and will not go back to the queue. A...
Development - 10-20-2020: Legacy BoldNet SOAP API (v2.1.20)
Issue Description: A customer who updated to 2.1.20 and ran into problems with the Address table update in their integration. It gave an error that it expected 20 fields and received 18. This is due to a change we made for PSIM. The issue is ar...
Development - 9-3-2020: ASAP-PSAP Update message (v2.1.18/v2.1.19)
Issue Description: A customer who updated to 2.1.19 to get the new MWC fixes found that we were not sending the Update message to the PSAP with the proper Incident number. This causes the PSAP to reject that message. This turns out to be a chan...
Development - 8-12-2020: Binary Video Log Broken (v2.1.18/v2.1.19)
Issue Description: A few customers have started having problems in the Web Client when viewing binary video. It is typically reported as a VCC problem, but the issue was actually just reading the log line in the MWC API. We had tried to fix a b...
Development - 7-17-2020: Interface Plano Fixes and Logging (v2.1.18)
Issue Description: Interface has been trying to get to a point where they can use the Web Client full time for alarm handling. They have seen several issues that have become critical to resolve. Lots of issues now tracked on Monday.com...
Development - 6-30-2020: Alarm Allocation Issue (v2.1.18)
Issue Description: Interface has been trying to get to a point where they can use the Web Client full time for alarm handling. They have seen several issues that have become critical to resolve. Broker was not checking the max alarms M...
Development - 6-10-2020: Manitou Web Client HotFix for OSU (v2.1.17)
Issue Description: If you follow a very specific sequence. As reported by the customer: Open Alarm Handling, make sure that it is active. Search for a customer and use the Advanced “put on test.” During the course of putti...
Development - 6-9-2020: AppServer HotFix for OSU (v2.1.17)
Issue Description: OSU is having a problem where they have an EAP to check for insched but this is not working properly. We found that they have a customer account AND dealer that both have the same serial no. This causes confusion when looking...
Development - 6-5-2020: AppServer where Contact X using callList Y will not display in EAP in alarm (v2.1.17)
Issue Description: We found that a fix to a bug where call lists that have the same name on a customer and on the authority, where the authority was also part of the customer call list inadvertently caused all call lists in an action pattern no...
Development - 6-1-2020: Fix for MWC inability to edit Autotext contact point types (v2.1.17)
Issue Description Error found with editing contacts through BoldNet if those contacts also have an autotext contact point. If a contact with an AutoText contact point is edited the number in the autotext field will be overwritten. When vie...