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
Customer Invoice Group (15399)
Product: SedonaOffice
Description: Add a dropdown at the customer level for invoice groups. When a new RMR is created, and the customer invoice group is set, the RMR that is created utilizes that customer's invoice group
Bugs
SedonaWeb Not Allowing Non-US Zip Codes (13343)
Product: SedonaOffice
Issue: When customers try to register a new account on sedonaweb, and they do not have a standard US zip code, the system errors and does not allow the registration
Solution: Ensure that when registering a customer user that is utilizing a zip code that is not a standard US code, the registration does not error and allows the registration
Orphaned Payments Version 6 (13859)
Product: SedonaOffice
Issue: Orphaned Transactions were getting stuck in a stale status where users could not void from the front end and resubmit
Solution: Resolved the portion of the Forte transaction process that was throwing the transactions into an orphaned state
Purchase Orders in Service Tickets Missing Address Line (14177)
Product: SedonaOffice
Issues: When creating a purchase order from a service ticket, the purchase order does not include the full warehouse address when being printed
Solution: Ensure that full address is included on printed purchase orders that have been created from service tickets
$0 Unapplied Cash Transactions Never Settle (14751)
Product: SedonaOffice
Issues: Users are able to submit unapplied cash transactions for zero dollars and submit them to Forte. Forte will approve the transactions, but will not settle them
Solution: When creating unapplied transactions, prevent users from completing the creation of the transaction if the amount is zero dollars
Cannot Edit Bills (15059) *Affected Loss Detection*
Product: SedonaOffice
Issue: If adding a bill with a costing type of job, but not attaching the bill to a job, the bill still went through the locking process as if it was attached to a closed Job
Solution: Check that the bill is actually attached to a job before it checks if WIP has been applied to lock the bill
Service Ticket Vendor Return Increments Issue (15056)
Product: SedonaOffice
Issues: When a vendor return is created from a service ticket, the issued quantity of the the part being returned is incremented instead of being removed due to the return
Solution: Changed the backend to count this action as returning the item, thus lowing the issued amount of that part instead of increasing it
Manitou Info for SO Accounts Pushed from Manitou (15124)
Issue: When creating an account in Manitou, then pushing that into SO, the Manitou Info button does not successfully trigger
Solution: We need for users to be able to access the manitou info area when the account is pushed into SO from Manitou the same way they would if the account was pushed from SO to Manitou
