The following changes will be released to Visma Severa's API in the next release:
General changes to API
Change (identifier) |
| GetEntitySchemaVersion method has been added to API. Use this method to compare if Visma Severa API has breaking changes in entities. This feature is recommended to be used in all integrations. Value is updated by Visma Severa when existing entities are changed. When value has been changed, update your service reference for your integration to work correctly. (2999) |
| Previously, when using Visma Severa API, one could get "Access denied" error from time to time when making API calls. Visma Severa API has been improved internally so that the error won't come anymore. (3309, 3086). |
| When API call is made and data is not found, Visma Severa API might return NotFoundException, null or an empty list. API documentation has been improved to tell how a method behaves when no data is found. At the same time various methods have been improved regarding this. (2696) |
| API documentation has been updated to contain better quality data. Unnecessary documentation has been hidden (for example constructors for Severa's exception classes), and missing documentation of interfaces and entities has been added. |
Interface changes
Interface name | Change (identifier) |
| IAccount | Inserting / updating account: Previously it has been possible to insert account rating that was not valid. This caused an exception in Severa's Account page. This has been fixed so that given account rating is validated and error thrown if it is not in the acceptable range, and API documentation has been updated. (3130) |
| IAccount | Inserting / updating account: Previously it has been possible to insert account with negative account number. This has been fixed so that only positive numbers are accepted. (3132) |
| IAccount | Inserting / updating account: Previously it has been possible to insert account with negative payment term and overdue interest. This has been fixed so that only 0 or positive numbers are accepted. (3133) |
| IContact | Inserting / updating contact: Previously it has been possible to insert contact with custom salutation. In Severa, salutations are translated to different languages by the system itself, and custom salutation caused issues. This has been fixed so that only "Ms.", "Mrs." or "Mr." are accepted as salutation, and API documentation has been updated. (2674) |
| ISettings | Removed from API, did not have any functionality. (2786) |
| ISearch | Removed from API, did not have any functionality. (2787) |
| IDictionary | Removed from API, did not have any functionality. (2702) |
| ILanguage | Was excluded from API documentation, now is visible. (2988) |
| IHourEntry | HourEntry has TaskGUID and PhaseGUID, which mean the same thing. When AddNewHourEntry method was used, using only PhaseGUID caused an exception. Method has been fixed to support both TaskGUID and PhaseGUID. (1715) |
| IInvoice | Setting invoice number: Previously, in a situation where the set invoice number was the same than organization's "next invoice number" in Severa's settings, next invoice number was not updated and organization could get two invoices with the same number. Logic has been changed so that "next invoice number" information is updated. (3284) |
| IItem | Deleting items: Previously it has been possible to delete items, which have been on read-only travel reimbursements. This has been fixed so that deleting such items is not possible anymore. (2674) |
| ICase | API documentation has been updated regarding ValidationExeption when deleting case or product. (3033) |
| ICase | Inserting / updating case: Previously it has been possible to insert expected value to case without giving sales status. This has been fixed so that sales status is required, otherwise expected value is ignored and not added to case. API documentation has been updated. (3290) |
| IProduct | API documentation has been updated regarding ValidationExeption when deleting case or product. (3033) |
| IProduct | DeleteTravelExpense, DeleteProduct: Previously it has been possible to delete travel or product from Visma Severa's settings through API even if the travel/product would have been used when making travel / product entries. This has been fixed so that deleting travels / products which are in use, isn't possible. (2782) |
Entity changes
Entity name | Change (identifier) |
| BusinessUnit | ShowLogoOnInvoices has been obsoleted, did not have any functionality. Showing logo functionality is on invoice template. (2172) |
| BusinessUnit | ShowLogoOnPdfReports has been obsoleted, did not have any functionality. (2172) |
| Case | OverdueInterest has been obsoleted, did not have any functionality. (3291) |
| InvoiceVAT | IncreaseBaseAmount method removed, did not have any functionality. (2972) |
| InvoiceDetails | Contains many properties that do not have any value ever, comments added. (2971) |
| HourEntry | HourEntry has TaskGUID and PhaseGUID, which mean the same thing. When AddNewHourEntry method was used, using only PhaseGUID caused an exception. Method has been fixed to support both TaskGUID and PhaseGUID. (1715) |
| Account | ImportID_GUID has been removed from the entity, did not have any functionality. (2985) |
| Address | ImportID_GUID has been removed from the entity, did not have any functionality. (2985) |
| Company | ImportID_GUID has been removed from the entity, did not have any functionality. (2985) |
| Contact | ImportID_GUID has been removed from the entity, did not have any functionality. (2985) |
| PhaseGetOptions | Added to API documentation. (2559) |
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.