Enhancements/Features
35318 | Update stored proc used by API to allow sites to be deleted
We updated the stored procedure Customer_DEL_from_API used by API to allow a specific site to be deleted.
If a site ID < 2 is supplied to the stored procedure, it functions the same as before, attempting to delete the customer.
If a site ID > 1 is supplied to the stored procedure, then these occur:
- Validates that the site ID exists.
- Validates that the site ID belongs to the supplied customer ID. If that is the only site on the customer, it functions the same as before, attempting to delete the customer.
- Validates that the site has no associated information (system, recurring, credit memo, item, cycle record, incident record, invoice, statement, job, point of sale record, or service ticket).
- If there is no associated information, the site is deleted.
(Note: This requires an update to SedonaWeb2.0 version 1.43.1.2.)
SedonaOffice Fleetmatics/Verizon Connect Reveal Integration
The SedonaOffice Fleetmatics/Verizon Connect Reveal integration has been updated to use Verizon Connect's latest REST API. The SOAP API is being deprecated by Verizon Connect. Customers must sign up for the new REST API.
Existing customers need to log in to the Verizon Connect Marketplace to create an integration user for the new REST API and select to share data with SedonaOffice.
This is the link provided by Verizon Connect to set up a new REST API integration user:
Once you have set up your new API Integration user, add your credentials to the Sedona Office Service Module.
- Go to SedonaOffice > Service.
- Go to VerizonConnect tab on the top menu.
- Click VerizonConnect Setup.
- Type your new Username and Password and select REST as the Active Interface.
The Base URL will default.
- To ensure the credentials/URL are correct, click the Test button.
- Save your settings to begin using the new Verizon Connect REST API integration.
Application Corrections (Corrected Bugs)
Accounts Payable
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Accounts Receivable
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| 35238 | 00077422, 77744, 77964, 77675 |
Cannot move Recurring Item to Another SystemResolved an error (You Cannot Move Cancelled Recurring) preventing users from moving a Recurring Item from one system to another on a Customer Account. |
| 35319 | 00077675, 77337 (?) |
Type 13 Mismatch error Attempt to Include Past Cancelled on RecurringResolved an error when using the Recurring "Include Past Cancelled" option, which was preventing the action from occurring. |
| 35338 | 00077943, 77580 |
Sub Item Of RMR Items have been duplicated on customer accounts since UpdateResolved an issue of additional Sub Item of line items being created if multiple RMR Items were linked to the same Sub Item Of under a Site on Customers' Accounts. |
| 35420 | Internal |
PCI Compliance utility hangsReverted some changes previously done in ForteService, which caused SEFT logging to be done at the wrong time, that could cause issues in the utility. |
Client Management
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Job Management
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Inventory
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| 35362 | 00078077, 78468 |
Equipment Install Dates changing to numbersResolved an issue with dates, so now when selecting Equipment under a customer's system and clicking on the Install Date header to sort by date, the information sorts correctly. |
Query Builder
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Report Manager
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Service
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Setup
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
eForms
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Sales Automation
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Time & Attendance
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Integrations
| Development ID | CRM ID | Resolved Issue |
|---|---|---|
| N/A | N/A |
N/A- |
Stored Procedures
Updated Stored Procedures:
- Customer_DEL_from_API
New stored procedures:
- n/a
Database Changes
- n/a
Special Upgrade / Installation Instructions
If upgrading from a SedonaOffice version prior to 6.0, the following related updates are also required:
Legacy SedonaWeb 1.0 - Be aware that if your company uses Legacy SedonaWeb 1.0 (latest version 2.7.80) with SedonaOffice version 6.2.0.8 and earlier, we recommend that you transition to using SedonaWeb 2.0.
Legacy SedonaWeb 1.0 is not for SedonaOffice 6.2.0.9 or later.
SedonaWeb 2.0/SedonaAPI 2.0 Setup - If your company uses the SedonaWeb/SedonaAPI 2.0, IT will update your SedonaAPI version at the same time as your SedonaOffice version. This is to ensure compatibility with the Sales Automation module.
If your company uses SedonaAPI in any manner (Sales Automation, Time & Attendance, eForms, or the SedonaAPI for integrations such as the Manitou integration), you need to update SedonaWeb/SedonaAPI to version 1.43.1 (or higher) when you update SedonaOffice to 6.2.0.12.
Performing Update - Once you have reviewed all 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
