ManitouNEO Version 2.0.7111.640
Special Instructions
The Distributer will not update the ManitouNEO web files!
You will need to run the ManitouNEO_setup.exe on each of the Manitou Servers running the web service, (IIS), to update the ManitouNEO and BoldNetNEO web sites.
Download Files
Issues Fixed in This Release
This section contains issues fixed for Manitou 2.0.0 (Update 33).
MediaGateway: Request to not convert 'A' to '0'
(Bug: 8190)
Product: MediaGateway
Issue: Customer requests that the MediaGateway not convert As to 0s
Solution: Commented out the code that does the conversions
Several Changes to the Standard Import Utility
(Bug 8462)
Product: Appserver, Standard Import Utility
Issue: Multiple issues within this particular version of Standard Import that do not have a workaround.
Solution: Corrected several issues within the Standard Import Utility
- Corrected "unique record" business rules for comments.
- Corrected "unique record" business rules for general schedules.
- Added ability to have a call list include a call list of another entity.
- Updated 2.0 SIU manual.
- Test Mode is not guaranteed to catch all possible exceptions that may happen during a full import, but should catch most. The App Server does not have a "test mode" option that would run through all the business rules but then cancel the transaction. The SIU itself does all the "test mode" validation. Unfortunately, multiple authorities is not something it currently validates. SIU will now inform of the error and gracefully rolls back the transaction for that customer. The import file can be corrected and that customer can be re-imported with no harm done. Added a "Test Mode vs. Full Import" section to the manual explaining this situation.
- Added validation to ensure either CPTYPENO or TYPETXT has been supplied. Error is reported in both Test Mode and Full Import, and will no longer halt the SIU in Full Import mode if neither is supplied.
- Business rule for "unique" passwords was removed in 2010, removed the validation from the SIU
- REGIONNAME corresponds to the FILEAS of an existing region in the database. Therefore it is correct that it should be capitalized. It is defined as a CODE field in the import specs, which should be formatted in the data as all caps.
This was actually a problem in the app server when retrieving the current time. This has been corrected. - Updated the 2.0 SIU to handle all action pattern details as the 2.1 SIU does. All item types / command types had not been fully implemented. Known issue that ITEMTYPE 0, CMDTYPE 5 does not import properly - generates an error.
Known Issues
This section contains known issues which are scheduled for a future update.
Adding a UserID on an account that does not have an Area won't save (Ticket: CAS-09346-N2T5R9)
This has been addressed in the 2.1 release.
Product: ManitouNEO
Issue: When attempting to add a UserID on a Contact, but no Area exists, the UserID doesn't save.
Launch URL is not passing parameters (Ticket: CAS-15479-X3D5G0)
This has been addressed in the 2.1 release.
Product: ManitouNEO
Issue: Action Pattern action LAUNCH URL is not passing in parameters as expected.
When searching for a Global Keyholder on a secondary contact point, they do not show in the search results (Ticket: CAS-13478-F1P2F8)
Product: ManitouNEO
Issue: When a Global Keyholder has more than one Contact Points, when doing a search for the non-primary number, the Global Keyholder is not returned in the search results.
BoldNetNEO: Allows saving OnTest entry with 0 hours and 0 minutes (Ticket: CAS-13554-P8H5R9)
This has been addressed in the 2.1 release.
Product: BoldNetNEO
Issue: Adding a reason for On Test but not adding any hours or minutes allows for saving. After saving while still in the account it shows the account is currently On Test. Have to exit the customer record and go back in for the On Test to go away.
