Follow

Api release notes for February 2018

GUID generator algorithm changes

To improve the performance of the SOAP API we have implemented Rijndael algorithm for GUID generation. The new algorithm lowered the API server's CPU usage approx. 30 %

The new algorithm will be in use as default for all new customers who take Severa API into use. Existing integrations will keep using the old RC2 algorithm.

If you know that your integration doesn't save the guids into your database, you can contact Severa customer support (severasupport@visma.com) and ask them to enable the new algorithm for you.

There are some integrations that are build by Severa team on top of the API and we will update those to use the new algorithm. This is done per customer and can only be done for those customers who are not using Severa API on it's own, or certain integrations that we know that store guids (for example Visma Business, Visma Global, Zendesk and Jira).

Interface changes

Interface name

Change (identifier)

Release date

ICustomer

  • New parameter "criteria" added. It includes following CustomerCriteria options:
    • AccountGroupGuids: A list of account group guids to filter the customers returned.

23.2.2018

ICase

  • GetAllCases query is optimized.
  • New parameter "criteria" added. It includes following CaseCriteria options:
    • OnlyActiveCases
    • OnlyCustomerCases
    • OnlyInactiveCases
    • OnlyInternalCases
    • SalesProcess: To get projects or sales cases. Get cases which are in specific sales process: InProgress, Won, Lost, NotSelected. NotSelected means that case does not have sales process defined. It's possible to use multiple statuses by separating them by comma, e.g. "Won,NotSelected", which means that all projects which has Won sales status or does not have sales process defined will be returned.

23.3.2018

IHourEntry

GetHourEntriesByDate query is optimized.

23.2.2018

IHourEntry

GetWorkDayInfoByDateRangeAndUserGUID query is optimized

23.2.2018

IUser

Updating user's email address will be ignored.

18.2.2018

Entity changes

Entity name

Change (identifier)

Release date

Case Class

New properties:

  • CaseCompanyCurrencyGUID
  • CurrencyShortformOfCaseCompanyCurrency

Description updated for:

  • CurrencyShortform: The ISO code of the case's invoicing currency.
  • ExpectedValue: Expected value in the case's company's currency.
  • CurrencyGUID: GUID of the invoicing currency of the case.

18.2.2018

Account, Company, Customer Class

Description updated for:

  • InvoicingVat: Invoicing VAT percentage. Given VAT percent must be found in API user's company.
  • ReverseCharge: Reverse charge setting for invoices made for the account. Reverse charge is set for the invoice sender country of the API user's company.
  • ReverseChargeDescription: Reverse charge description for invoices made for the account. Reverse charge description is set for the invoice sender country of the API user's company

18.2.2018

HourEntry Class

New properties:

  • UnitCostInOrganizationCurrency
  • UnitCostInUserCompanyCurrency
  • UnitCostInInvoicingCurrency
  • CostCurrencyShortformOfOrganizationCurrency
  • CostCurrencyShortformOfUserCompanyCurrency
  • CostCurrencyShortformOfInvoicingCurrency
  • UnitPriceInUserCompanyCurrency
  • UnitPriceinCaseCompanyCurrency
  • PriceCurrencyShortformOfOrganizationCurrency
  • PriceCurrencyShortformOfUserCompanyCurrency
  • PriceCurrencyShortformOfCaseCompanyCurrency
  • PriceCurrencyShortformOfInvoicingCurrency

Description updated for:

  • UnitCost: Hour entry's unit cost in case's company's currency.
  • CostCurrencyShortform: The ISO code of the cost's currency in case's company's currency.
  • UnitPriceInBaseCurrency: Unit price in organization's currency
18.2.2018

Employment Class

New properties:

  • CompanyBusinessUnitCode
  • CompanyBusinessUnitGUID
  • CompanyBusinessUnitName
18.2.2018

Item class

New properties:

  • UnitCostInOrganizationCurrency
  • UnitCostInUserCompanyCurrency
  • UnitCostInInvoicingCurrency
  • CostCurrencyShortformOfOrganizationCurrency
  • CostCurrencyShortformOfUserCompanyCurrency
  • CostCurrencyShortformOfInvoicingCurrency
  • UnitPriceInOrganizationCurrency
  • UnitPriceInUserCompanyCurrency
  • UnitPriceInInvoicingCurrency
  • PriceCurrencyShortformOfOrganizationCurrency
  • PriceCurrencyShortformOfUserCompanyCurrency
  • PriceCurrencyShortformOfCaseCompanyCurrency
  • PriceCurrencyShortformOfInvoicingCurrency

Description updated for:

  • UnitCost: Unit cost of a single unit in case's company's currency, the money we have to pay out when getting this. UnitCost does not include VAT.
  • UnitCostVatIncludedAmount: Unit cost of a single unit in case's company's currency, the money we have to pay out when getting this. UnitCost does not include VAT. This read-only field is available only when managing travel reimbursements.
  • CostCurrencyShortform: The ISO code of the cost's currency in case's company's currency.
  • UnitPrice: Unit price of a single unit in case's invoicing currency, the money we ask for the customer when selling this. UnitPrice does not include VAT.
  • UnitPriceInBaseCurrency: Unit price in base currency (of the case). Usually same as UnitPrice, unless UnitPrice is in different currency than case is using.
  • PurchaseVAT: VAT percent of the cost of this item. Given VAT percent must be found in User's company. UnitCost does not include VAT.
  • VAT: VAT percent of the price of this item, used when item is invoiced. Given VAT percent must be found in Case's company. UnitPrice does not include VAT.
18.2.2018

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Powered by Zendesk