Special Upgrade / Install Instructions:
If your company uses the SedonaCloud API, IT will update the SedonaCloud version at the same time as your SedonaOffice upgrade. This is to ensure compatibility with the all modules utilizing SedonaCloud.
Supported Environments:
Version Support
** This version of SedonaCloud requires SedonaOffice version 6.1.0.60 or above **
Minimum System Requirements:
• Server is on Microsoft .Net 4.6.1
Features:
None
Enhancements:
Removed regex for CustomerPostalCode in the api/paymentmerchant/addcreditcard endpoint. This will resolve issue where postal codes that include a hyphen are being rejected.
Increased the default ODataPageSize limit from 250 to 500. This will allow larger record sets to be returned.
Bugs:
Cell Phone does not save in SedonaWeb 2.0 (17489) [3584]
Issue: In SedonaWeb 2, when the user goes to Settings and My Account and adds a cell phone number it doesn't actually save. When you click on the save button it clears out the cell phone # field.
Solution: Modified the code that wasn't displaying the Cell Phone number. Also, modified the code to update the Customer Contact table with the customer's information (it was updating info in the SedonaCloud database's ASPNetUsers table and the SEdonaOffice database's AR_Customer_Bill table).
Notes entered on ticket in SedonaWeb 2.0 do not add to the SedonaOffice Ticket (17490) [3583]
Issue: When you create a ticket in SedonaWeb 2.0 the note are not added to the ticket in SedonaOffice and when you view the notes in SedonaWeb 2.0 they show as resolution notes.
Solution: Refactored code so Service Ticket Notes and Note Access levels are being handled properly.
Adding link in Service Tickets in SedonaWeb2.0 includes HTML Tags in SedonaOffice (17492) [3582]
Issue: When creating a service ticket from SedonaWeb 2 you have the ability to add a link, however when you attempt to use this it shows some coding within the note.
Solution: Changed the Kendo Editor to a simple Textarea. Using the Kendo Editor caused encoded markup to be stored in the database (causing potential string truncation issues as the database is only 255 characters). This encoded markup was never decoded again when used in the view Service Ticket in SedonaCloud/Web 2.0 (the customer comment was displayed with confusing encoded markup).
UseCompanyPrefix instead of UseUrlPrefix does not work (17858) [Internal]
Issue: When the UseUrlPrefix setting is set to false, the CompanyPrefixKey in the URL\Route should be used but is not.
Solution: Fixed an issue with companyPrefix in RouteAttribute that caused an issue with MvcConfig.CompanyPrefixKey getting the value from the RouteData.
Invoice_Group_Number property on AR_Item could not be set to a 'System.Int32" value (18651) [12759]
Issue: We are receiving the following error message when attempting to utilize the SedonaCloud API by calling /api/CustomerInvoice/ "The 'Invoice_Group_Number' property on 'AR_Item' could not be set to a 'System.Int32' value. You must set this property to a non-null value of type 'System.Byte'."
Solution: Adding sql scripts into schema update portion of SedonaCloud to ensure that the Invoice_Group_Number columns are INT datatype instead of TINYINT. This update has not been consistently applied to the SedonaOffice database. Also, add column for Invoice_Group_Number to AR_Customer since it can be missing in some databases.
T&A Dispatch to SedonaOffice service tickets not showing in SedonaOffice (20083) [Internal]
Issue: The SO ticket is not being updated that the ticket has been dispatched. Interesting, though, is that I don't see any errors being thrown, but the SO ticket is definitely not updated that is it dispatched, and T&A shows that it is.
Solution: Changed UTC properties in Dispatch to use private variables. These private variables will be checked for null on GETs, if null then the corresponding non-UTC value will be used to calculate and assign a UTC value to the private variable, this private variable will then be returned from the GET. The SETs will specify the private variables.
