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
Forte Submission Process Performance (7044)
Product: SedonaOffice
Description: Improving the speed of submitting transactions through the Forte submission process by implementing an asynchronous model for the HTTP client
Bugs
PO Expense GL Account Dropdown Not Working (5804)
Product: SedonaOffice
Issue: When creating an expense PO from a job, the Expense tab GL Account dropdown list was not available
Solution: The GL account dropdown in the expense tab is now there as expected
Aging and Collections Not Updating (10616)
Product: SedonaOffice
Issue: The system is not automatically updating the customer aging and the customer collection queues when eft transactions are posted
Solution: We corrected the aging to run correctly for transaction types and ensured that it wouldn't run multiples for transactions that are applied to more than one invoice
Previously Funded/Z Transaction Duplicates (11057)
Product: SedonaOffice
Issue: Some previously funded transactions were being entered twice when the settlement process was run as new EFT transactions and were automatically being marked as settled.
Solution: To resolve this issue, many things were corrected: Corrected setting properties for cloned transaction. Corrected linking Deposit batch to new transaction. Corrected clearing trace number on old transaction, this was causing duplicates as it would see a transaction matching the trace # in the wrong state during settlement processing. Corrected Aging not running for certain types of transactions. Corrected Aging running multiples if transaction applied to multiple invoices. Unified UserCode used by SedonEFTService to SedonaEFTService. Added Ability to Mock responses in Forte TestService. Removed some dead code clutter. Developed a Script for data correction to properly clear trace numbers on old transactions that should have been cleared
Customer Aging Routine Locking Sedona (11187)
Product: SedonaOffice
Issue: The issue appears to be that the stored procedure Single_Customer_Age_Routine is taking too long to execute, for customers with a large number of invoices. This stored procedure is run each time a service ticket invoice is created. The invoice creation fails because the stored procedure blocks other procedures from executing
Solution: Removed duplicate queries and replaced a slow query within the stored procedure to decrease load time from roughly 8 minutes to a few seconds
