Special Upgrade / Install Instructions
If upgrading to SedonaOffice 6.0 and higher, the following related updates are also required:
FSU Updates - iOS devices must be on iOS version 11 or newer. Please also check the app store for any updates to your FSU app
SedonaWeb - If your company uses SedonaWeb, IT will update your SedonaWeb version at the same time as your SedonaOffice version. This is to ensure the highest level of PCI compliance throughout all applications
SedonaCloud/SedonaAPI 2.0 Setup - If your company uses the SedonaAPI, IT will update your SedonaAPI version at the same time as your SedonaOffice version. This is to ensure compatibility with the SalesAutomation module.
If you are not a SedonaCloud customer, please review the requirements for the new API before requesting the update. For a copy of pre-install requirements please contact: sedonaoffice.support@boldgroup.com
Performing Update - Once you have reviewed all of the above information, and followed all preparation steps, contact SedonaOffice support. We will note on your account that you have received the Release Notes and are ready for update. SedonaOffice IT will then contact you to schedule your update.
Supported Environments
Minimum System Requirements:
• Server is on Microsoft .Net 4.6.1
Features and Enhancements
Manitou Integration Adjustment (7618)
Product: SedonaOffice Manitou Integration
Description: Area Column Added to Zone List Grid to show the area information as entered in Manitou
Bugs
EFT Auto Process to Open an Accounting Period (8497)
Product: SedonaOffice
Issue: When the EFT auto process runs, if the current accounting period is not open, the transactions will all fail, and the logger is fill with errors. Also, when submitting payments through SedonaCloud, submission fails but no reason is given
Solution: The PaymentClient class called by SedonaWeb and SedonaCloud will attempt to automatically open the accounting period if possible. If it is not possible (because the fiscal year needs to be opened), the PaymentClient will throw an AccountingPeriodClosedException. The service will then write a message to the Service log that Fiscal Year needs to be opened and complete without submitting or settling any transactions. (It will not update the last transactionstart and transactionend date ranges for settlements, so the range on next run will include days skipped due to closed fiscal year.)
PCI Compliance Update Logging Permissions (9180)
Product: SedonaOffice
Issue: The PCI Compliance updater is have problems creating log files
Solution: The PCI Compliance updater has had the log file location changed so the log writes to the desktop. This change was made due to permission file system problems when the PCI Update was run from a server
Submitted Date in Transaction Summary Issue (9184)
Product: SedonaOffice
Issue: In the transaction details we are showing a submitted date of 1/1/1900 on all transactions that have not been submitted
Solution: Edited Formatting function to look for proper invalid date codes. Function was using DateTime.MinValue which is not what we store in the database for null/invalid dates. The details will now be empty if the transaction has not been submitted
Auto Process Non-Recurring Invoices Issue (9217)
Product: SedonaOffice
Issue: The Auto Process Non-Recurring Invoices process is also processing cycle invoices
Solution: Updated stored procedures utilized by the Auto Process Non-Recurring Invoices to ensure it does not process cycle invoices
