Enhancements/Features
30793 Registration Code Request Email
There is a new process for customers to register an account in SedonaWeb 2.0. For customers to register, they need to request their customer number and registration code.
To start, on the Log In screen they need to click the line “Register as a new Customer?”:
On the Register Create a New Account page, customers complete the required fields: Customer Number, Registration Code, First Name, Last Name, Email, and Password. If customers do not know their customer number, they click the link “Email my customer number”:
On the Email Customer Number page, customers enter their email address or phone number, which must match those on file, and click Submit:
When customers have their customer number, they can click the link “Email my authentication information”:
Customers enter their customer number, email address, and click Submit:
When customers have both their customer number and registration code, they can create a new account.
Corrected Bugs (Application Corrections)
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| ID | CRM ID |
h5paragraph |
SedonaAPI
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| 30243 | 00052199, 56281 |
Some changes are not showing up in RMR HistoryResolved this issue so that SedonaOffice will only bring back the tracking information if the RMR Amount is greater than 0. |
| 30766 | 00058412 |
POST /api/CustomerRecurring allows creation with no site or systemReworked the validation for the CustomerRecurring endpoint, which writes to the AR_Customer_Recurring and AR_RMR_Tracking tables, to ensure that the validations that occur in SedonaOffice when a customer recurring is created are also checked when using the API to create a customer recurring. |
| 31569 | INTERNAL |
Add/Update service ticket is incorrectly forcing the system's service company/level (related 30076 SX Mobile)Reolved this by not forcing system's service level and company to the service ticket when it is created or updated. The system's service level and company are used only if the Company or Service Level Id is not supplied in the payload (null or <2). |
SedonaOffice
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| 24920 | INTERNAL |
SedonaOfficeContext GetDBColumns() code needs to run on Company add/updateThe SedonaOfficeContext.GetDBColumns() should be executed not only on service startup, but also when a new company is added to SedonaCloud. Possibly also when an existing company is updated, especially if involves a connection string change. The code that checks/updates the SedonaOffice database schema when SedonaCloud is first started will now be executed when a new company is added successfully via the Submit button and when the connection string of an existing company is changed and saved successfully via the Submit button. |
SedonaWeb
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| 22853 | 00026567 |
Cannot delete a custom role groupResolved this issue by making sure that the role group could be deleted and that there are not any users assigned to it. |
| 26953 | 00044276 |
API Logs not showing correct timesFixed the Time Stamp column on the API Logs, which had been showing the month number as the number of minutes. |
| 28027 | N/A (add to release notes anyway) |
Add CustomerRelation endpointsAdded GET /api/CustomerRelation and GET /api/CustomerRelation/{id} endpoints. |
| 28039 | N/A (add to release notes anyway) |
Add GET country endpointAdded GET /api/country and GET /api/country/{id} for users to know what the appropriate country value should be when submitting address information. |
| 28182 | N/A (add to release notes anyway) |
Add GET TransmissionFormat endpointAdded GET /api/TransmissionFormat and GET /api/TransmissionFormat/{id} endpoints. |
| 29791 | 00050495 |
Customers can view incomplete invoices on SedonaWeb 2.0Customers can no longer view incomplete invoices as all places that show invoice information have been changed to exclude incomplete invoices. |
| 29914 | 00052187 |
Invalid page when clicking role group button - is not using prefixResolved this issue by correcting URLs with missing company prefix in all areas - company user, customer user, master customer user. |
| 30478 | 00055506 |
Changes for Manitou Dealer Billing PostModified POST /api/CustomerInvoice/AutoInvoiceBuffer to receive the appropriate data from Manitou to post dealer billing invoices and to call the new Auto_Invoice_Buffer_SC stored procedure in SedonaOffice. This correction requires updates to SedonaCloud (1.43.0) and Manitou (2.1.36). |
| 31295 | 00060796 |
POST Customer allows Customer to be created with no Bill To recordsResolved this issue with the following changes: If the bill-to record fails to save, it will now rollback the customer record so that it is not saved either. Resolved an issue with the error message from adding the bill-to that was not being retrieved. Because a log record is already written indicating "customer added"; there is now a second log record written indicating "customer deleted due to rollback". |
| 31307 | N/A |
Remove negative sub-item validation from customer RMRResolved this issue by removing the restriction that sub-items cannot have a negative amount. |
| 31416 | N/A (add to release notes anyway) |
AR Setup Processing Cycle Beginning Day not honored by Post RMR endpointResolved this issue by changing the validation for BillOnDay to the following rules: |
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 modules utilizing SedonaCloud.
Supported Environments
- This version of SedonaCloud requires SedonaOffice version 6.2.0.9 or above.
- Minimum System Requirements: Server is on Microsoft .Net 4.6.1
