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
Bugs
Issues with AP Bill Form (10613)
Product: SedonaOffice
Issue: In certain scenarios, the AP bill form does not allow you to enter or edit an amount for items on the bill. This may be caused by multiple grid column update events being triggered when the amount, rate or quantity values are changed. Because the error is occurring when SedonaOffice is run from a terminal service, these multiple events could possibly cause a race condition, that might result in this behavior
Solution: Implemented code to eliminate the possibility of a race condition with these grids
Suppress Error on Forte Checkout web page unload (11674)
Product: SedonaOffice
Issue: Since Forte's last update to the Checkout API, our embedded web browser displays a scripting error message when it attempts to close the embedded browser window. This is a nuisance error, as it does not prevent the Payment method from being saved in either DEX/Checkout or the SedonaOffice database, so it may be safely ignored
Solution: Suppress the scripting error popup dialogs via a property on the WebView control providing the embedded web browser
Forte Transactions Submitted as Authorize (11884)
Product: SedonaOffice
Issue: Batch tranactions were getting submitted as "Authorize" instead of "Capture"
Solution: Corrected the Asynchronous auto-submission code so that a transaction with neither Is_Sale or Is_Credit marked as true is a valid state and will correctly process
Cancelled Masters Not Set to Inactive (11938)
Product: SedonaOffice
Issue: If a Master Account is cancelled, when trying to link a customer to a valid master account (edit customer setup from the customer explorer), the Cancelled Masters are appearing in the list
Solution: Ensured that cancelled master accounts are set to inactive. To exclude master accounts that have been canceled before this change, we've also excluded cancelled customer accounts from master account query
Job Task Field Restriction when Reopening a Closed Job (11940)
Product: SedonaOffice
Issue: From the closed job queue, users can re-open a closed job by clicking on the Re-Open button in the task section of the job and they are then presented a box with a drop-down list of tasks to select from. If the user, instead of selecting from the drop-down list, types in the task box the name of a new task and saves, a new task entitled "N/A" is added to the job that cannot be edited or removed
Solution: Changed the Job Task dropdown property to not allow input in the text field
SedonaEFTSErvice Error Loading Database List if Cannot Open Accounting Period (12110)
Product: SedonaOffice
Issue: Due to database error with Accounting Periods, database collection failed and would not load
Solution: Added error handling to identify what database error is being thrown and implemented code to prevent one database failure from causing the entire database collection to fail
EFT Process not Locking Records (12142)
Product: SedonaOffice
Issue: Some transactions are not being submitted due to the transaction being locked
Solution: Updated error handling to provide further detail as to why transactions aren't being submitted, as well as adding some preventative measures to the lock mechanism with transactions
