Knowledgebase:
Storman v9.3.02
Posted by Jonathon Wildon, Last modified by Jonathon Wildon on 13 September 2017 08:44 AM

StorMan v9.3.2

Please find below, our Release Notes for this version. Should you have any questions or comments about this release, please get in touch with your nearest StorMan office.

Release Notes

Automated Payment Methods & Processing

  • Cash Sale transactions will now only save if all items contained within have the same transaction date.
  • CardSave (UK) processing has been updated to support their latest security requirements.
  • The CVV2 field is now required in order to process credit card payments with CardSave (UK).
  • GoCardless (UK) is now supported on the Apple Mac operating system.
 

Daily Processing

  • The Daily Processing summary screen now shows the amount to bill for Credit Sales.
  • Daily Processing can now be run for multiple sites at the same time (when operating in a StorMan MultiSite or StorMan MultiView environment).
  • Check Activity, when run on the StorMan Server, now notifies the operator when it has completed.

Ezidebit

  • Fixed several minor issues with the Ezidebit interface that caused errors with Customer Profiles.
  • It is now possible to manually trigger a Bank Account Direct Debit from a Customer's 'Bank Account on file', if stored on the AutoPay & Notices tab (similar to the "Use card on file" function for Credit Card Direct Debits).

Insurance

  • Previously, StorMan would always display "Insurance" whenever the Analysis Code tagged with "IN" was used; ignoring the description that had been entered by the operator. This has been fixed.
  • Previously, Other Recurring Charges were not allowing staff to edit Insurance Charges, even if their permission was set to allow this. This has been fixed.
  • If the Insurance Rates module calculates the monthly insurance charge as being equal to $0.00, StorMan will no longer create an Other Recurring Charge.
  • The Insurance Rates Module used to display an error when the Start Value matched the Previous End Value. This has been fixed.
  • The Copy To All button for Insurance Rates (in a StorMan MultiSite or StorMan MultiView environment) now functions correctly.
  • The buttons on the Re-Calculate Insurance screen (in the Insurance Rates Module), have been reworded to better-reflect their respective functions.
  • Operators can now control how StorMan rounds insurance; either standard, up or down. This is a new field in System Setup.

Marina

  • Subletting previously did not allow the operator to proceed when an Agreement had more than one Berth. This has been fixed.

MYOB

  • StorMan now supports exports to MYOB versions 2014 and greater.

Reports & Reporting Functions

  • Periodic Reporting will no longer trigger unless a Send Code has been setup under the Email & Event Log Setup screen.
  • The Rental Audit Report now uses the correct date in its default setting.
  • The Rental Variation History Report no longer generates when the operator uses the Cancel button.
  • The Can't Modify Prior To Date used to prevent the generation of old Banking Reports that were created prior to the current Can't Modify Prior To Date. This has been fixed.

SMS

  • The Modify Customer dialog now displays a mobile phone icon for sending an SMS to the customer.
  • Database references are now easier & quicker to insert in SMS Notices. Simply choose the reference from the list provided and it will be inserted automatically.
  • The 160 character limit for SMS Notices has now been removed; there is now no limit.

Other

  • Email address validation has been updated to accommodate new top level domains (e.g.: .global) that are longer than three characters.
  • Backups were not working correctly for users running StorMan on the Apple Macintosh Operating System. This has been fixed.
  • The Facility Sort Order field, used in StorMan MultiView environments, can now only be adjusted by StorMan Staff.
  • Bulk Discounts were previously not rounding to two decimal places. This has been fixed.
  • Previously, the Unconfirmed Receipts list that generates during Daily Processing was not showing transactions from Reservations. This has been fixed.
  • Previously, the Billing Plan Discount prorata did not calculate correctly when removing a Berth / Unit / Vault from an Agreement. This has been fixed.
  • Previously, merchandise sales that encompassed more than one Merchandise Discount Plan were not calculating the discounts correctly. This has been fixed.
  • Previously, the Show Rented Berths / Show Rented Units / Show Rented Vaults function (on a Sales Enquiry, as well as on a Reservation and an Agreement) did not display all Berths / Units / Vaults. This has now been fixed.
  • Invoice Numbers were being cut off on a number of Operating Systems. This has been fixed.
  • The Event Log Exceptions Report used to cause a Runtime Error. This has been fixed.
  • The Agreement Balance Owing field no longer displays an incorrect value when opening an Agreement.
  • Various minor display issues have been fixed & various minor user interface adjustment have been made.

 

Impact Statement

For clients coming from StorMan 8.x > 9.3.2:

  • Web Services (API's) have been re-written. Clients who use our API's to link online services with their copy of StorMan will be required to update their API's. For more details, please contact your web developer. New API documentation: #OLSAPI01.
  • Clients using StorPay will require a Web Services Password be added to their system StorMan will perform this work for you, at the time of the upgrade. Note to StorMan Staff: A Web Service password is required to be entered in SU, as well as in System Setup.
  • The upgrade may take a significant amount of time depending on the speed of your computer & whether your existing database requires maintenance work first.
  • Due to the new graphics technology used, you will need to redraw any Custom Items on your Facility Map, as they will be lost during the upgrade. Custom Items refer to objects other than units and may include lines, boxes, shapes, text, etc. Furthermore, any Custom Headers on Invoices, Custom Footers on Invoices & any Receipt Customisations will be lost. You will need to recreate them.
  • Due to the new HTML email system used by StorMan, you will need to check the setup of each Email Notice to ensure it has converted properly.
  • The way the Deposits Held Report works has changed slightly. More on this: #RPTDHR01.
  • Customers that are currently on AutoPay will now need a valid "from" date for their AutoPay authorisation, otherwise they won't be able to process automatically. The "from" date can be set on the AutoPay/Notices tab (the field appears when you enable AutoPay) on the customers agreement.

 

For clients coming from StorMan 9.1.x > 9.3.2:

  • Web Services (API's) have been re-written. Clients who use our API's to link online services with their copy of StorMan will be required to update their API's. For more details, please contact your web developer. New API documentation: #OLSAPI01.
  • Clients using StorPay will require a Web Services Password be added to their system StorMan will perform this work for you, at the time of the upgrade. Note to StorMan Staff: A Web Service password is required to be entered in SU, as well as in System Setup.

 

For clients coming from StorMan 9.2.x > 9.3.2:

  • Web Services (API's) have been re-written. Clients who use our API's to link online services with their copy of StorMan will be required to update their API's. New API documentation: #OLSAPI01.

 

For clients coming from StorMan 9.3.x > 9.3.2:

 

  • Web Services (API's) have been re-written. Clients who use our API's to link online services with their copy of StorMan will be required to update their API's. New API documentation: #OLSAPI01.
(0 vote(s))
Helpful
Not helpful

Comments (0)