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
Z-Transaction Issues (6298)
Product: SedonaOffice
Issue: When a z-transaction is reversed the Invoice is reopened and the application creates a negative deposit payment entry for the return. The original Forte response code is being overwritten by the reversal of the previously funded transactions that leaves no way for the user to trace the previously settled transaction. If the original transaction was coded as an unapplied cash, then applied to open invoices, the application creates a miscellaneous invoice and that miscellaneous invoice has no detail data attached and no GL register. If the original invoice is paid by another transaction during the time the z-transaction is being posted the application will create a miscellaneous invoice. The AR_deposit GL register is off when z-transactions are being posted for some reason the deposit batch is removing the transactions attached
Solution: Properly post Z-Transactions using the PostPreviouslyFundedPayments class. Replace the existing methodology that was treating a z-Transaction more like a refund. Corrected the issue were the Response from the Settlement was overwriting the initial response form the processor provided on submission. This also contains considerable clean up of the code to help Identify the problem and support future maintainability. A significant amount of obsolete code (much of it marked for future deletion) has been pruned out. The Main Settlement look has had the logic broken into smaller chunks (ie calls to separate methods to perform tasks instead of all the logic being in a single method)
Settlement Service Abnormal Fail Logging Error (9825)
Product: SedonaOffice
Issue: An exception is being thrown when logging an abnormal fail in the Settlement Service due to the length requirements of the message field in the table 'SEFT_Reconciliation'
Solution: Increase the 'message' field to 300 characters in the database and added some additional error handling
On Order Quantity Adjustment Issues (2371)
Product: SedonaOffice
Issue: On order quantity for parts on purchase orders was not working correctly for package-quantity parts when removing them from the purchase order. It was decreasing the on order quantity by the quantity of packs instead of the quantity of total parts
Solution: Ensured that the purchase order On Order quantity accurately accounts for package-quantity parts
Repair Order Not Displaying in Parts Explorer (9217)
Product: SedonaOffice
Issue: Repair orders can be created with an empty quantity field
Solution: Added a check for an emtpy part quantity field when saving repair orders
Resolved Opportunity not using proper value of Res/Com on Customer (6641)
Product: SedonaOffice
Issue: On the customer and site created, the Residential/Commercial setting on the prospect is not flowing through. Appears application is using the default in sedonasetup data entry defaults
Solution: Fixed the customer creation from a resolved opportunity to import the commercial/residential customer type field
Purchase Order Tree Errors Due to Too Many Warehouses (6761)
Product: SedonaOffice
Issue: If a dealer had too many warehouses, the purchase order tree would throw an error
Solution: Increased the warehouse list maximum for the purchase order tree
Service Level Sorting Format (6943)
Product: SedonaOffice
Issue: When clicking in the Other Charges column header to sort on the service level grid in the setup tables, the data changes from money format to integer format
Solution: Fixed column tags of Service Level form in SedonaTables, so currency columns would retain proper formatting after being sorted
Job Notes Error (9567)
Product: SedonaOffice
Issue: In Sedona Jobs, if the two notes happen to have identical note text but different Note Types, users could not save the second Job Note of identical text to a job
Solution: Ensured that two notes with the same text but different job types could be saved
AP Bills Incorrect Terms w/Credit Card (9933)
Product: SedonaOffice
Issue: When a bill is paid by a credit card, the new bill on the credit card vendor shows the credit card vendors terms correctly in the terms field, but calculates them incorrectly in the payments due field. The payment due field is still calculating based on the terms for the original bill on the original vendor
Solution: Set credit card bill due date based upon the credit card vendor terms
Warehouse City Containing Single Quote Causes Error (10154)
Product: SedonaOffice
Issue: When adding a new warehouse, if the city contains a ' (e.g. St. John's), a runtime error occurs
Solution: Properly handle a single quote in a warehouse city name
Service Ticket Dispatched on a Holiday Uses Regular Rate Labor Cost (10156)
Product: SedonaOffice
Issue: When dispatched on a holiday, labor cost is still utilizing regular labor costs
Solution: Ensured that when holiday, the holiday labor cost is being utilized
Sorting Job Status Column in Job queue replaces status with 0 (10505)
Product: SedonaOffice
Issue: When viewing either Open Jobs or Unscheduled Jobs in the Job Queue, if you sort the Status column, all values are replaced with 0.00
Solution: Ensuring that when sorting the Job queue by job status, the values still populate
