...
In this article:
10.4.0 Release Notes
Change Highlights
...
Deprecated APIs:
v5/Payment/RetryRule (Get)
v5/Payment/RetryRule/Paged (Get)
v5/Payment/RetryRule/Paged/Detail (Get)
v5/Payment/RetryRule/{id} (Get)
v5/Payment/RetryRule/{id}/Detail (Get)
v5/Payment/RetryRule (Post, Put, Patch, Delete)
v5/Payment/RetryRule/{id} (Post, Put, Patch, Delete)
v5/RetryRule (Get, Post, Put, Patch, Delete)
v5/RetryRule/{id} (Get, Post, Put, Patch, Delete)
v5/RetryRule/Paged (Get)
Updated APIs:
v6/AccountsReceivable/Terms (Get, Post, Put): Removed PaymentRetryRuleId, PaymentRetryRuleName
v6/Account/Package (Get, Post, Put, Patch): The API will set the BillingActivationType automatically. Added BillingActivationTypeId, BillingActivationTypeName
v6/Account/SharePlan/Paged/Detail (Get): Added BillingActivationTypeId, BillingActivationTypeName
v6/Account/SharePlan/Paged/<Id>/Detail (Get): Added BillingActivationTypeId, BillingActivationTypeName
v6/Usage/Bucket/Base/Paged/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Usage/Bucket/Base/{id}/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Usage/Bucket/SharePlan/Paged/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Usage/Bucket/SharePlan/{id}/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Account/SharePlan/Paged/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Account/SharePlan/{id}/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Account/Service/Usage/Bucket/Paged/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Account/Service/Usage/Bucket/{id}/Detail (Get): On a Details request, IsBytesInBinaryUnit will be present if it is relevant to the SharePlan or UsageBucket. This is primarily a field to support the AdminPortal UI and indicates whether data units are in binary units (e.g. kibibytes) or non-binary (e.g. kilobytes). Added IsBytesInBinaryUnit
v6/Account/Package/View (Get): Added BillingActivationTypeId
v6/Account/Service/View (Get): Added BillingActivationTypeId
v6/Account/Contract (Get, Post, Put, Patch): API defaults to ‘Fixed’ charge type. Added ContractCommitmentPenaltyChargeTypeId and ContractCommitmentPenaltyChargeTypeName
v6/Contract/Commitment (Get, Post, Put, Patch): API defaults to ‘Fixed’ charge type. Added ContractCommitmentPenaltyChargeTypeId and ContractCommitmentPenaltyChargeTypeName
v6/Extension/Attribute (Get): Added CreatedByUserId, CreatedByUserName and Created
v6/Credit/Note/Download (Get): Added AccountId and AccountName
v6/ReportDefinition (Get, Post, Put): Added IsPrompt
v6/Report (Get, Post, Put, Patch): Added IsPrompt
v6/Tax/Vendor (Get, Post, Put): Some sensitive fields are not returned on Get. Added HasCredentialsSet
v6/Usage/Unit (Get): Added IsBytesInBinaryUnit
New APIs:
v6/Contract/Commitment/PenaltyChargeType (Get)
v6/DataImport/Usage/<Id> (Post): allows usage records to be posted by API and then transformed, mediated and rated by the system. The feed value specified in the request will determine the data profile to use
For additional API documentation please see the API Reference documentation on logisense.com.
10.4.2 Release Notes
Change Highlights
Product Catalog Enhancements:
Package Quantity Feature:
Added a 'Allow Quantity' setting on the Options tab of the Packages screen under the product catalog
This setting acts as a multiplier for billing so that the number of services in the package can be billed at the quantity specified (e.g. a package with one service and a quantity of ten set will generate one transaction/one invoice line item at ten times the normal service charge amount
This setting can only be enabled on packages configured with non recurring charges at this time
This setting can only be enabled for non-usage based NRC services
Quantity has been added to the Account Package data source to allow reporting on package quantities
Account packages can be imported with a quantity value provided so long as the quantity value is supported for the given package configuration (i.e. the package contains only non-recurring, non-usage based services)
Package quantities will be listed in the Customer Portal
Account Enhancements:
Transaction and Credit Quantities:
Added a 'Quantity' field to the Transactions and Credits screens so that multiple transactions/credits of the same type/amount can be added at once
Quantity tokens have been added so that quantity values can be displayed on invoices and credit notes
The maximum quantity value that can be set is 10,000
Quantity has been added to the Invoice Item data source for reporting purposes
Transactions and Credits with a quantity set can only be fully reversed. Partial reversals are not supported when quantity is used
Tax Enhancements:
Tax Adjustments:
Added a Tax Adjustments button on the Transactions screen which allows zero dollar transactions to be created with a user defined tax amount
positive and negative tax adjustments can be made
Tax Adjustments can be viewed on the Transactions tab and reversed
Tax adjustment invoice items can be imported into the system
Tax adjustments are not submitted to Avalara. The 'Tax Adjustment Reconciliation' report can be used to reconcile taxes with the compliance reports in the Avalara Communications Customer Portal
AvaTax Incorporated Configuration:
Added an 'Incorporated' option to the Address tab on the Contact screen which is displayed when AvaTax is configured as the tax vendor
When this setting is enabled it will indicate to AvaTax that the customer is inside an incorporated city area
See the Avalara user manual for more information
Other Enhancements and Fixes
Validation improvements
Limited usage identifier searches in the account search to a maximum of 500 identifiers at a time
Fixed an issue introduced in version 10.4.1 that could result in an account-package with optional services having an incorrect Next Bill Day after voiding an invoice
Fixed an issue where voiding an invoice which contained billing activation charges would clear the Billed Through and Usage Billed Through dates on the related account-package when the billing activation bucket was configured with only a time condition
Added the ability to configure a default sort column on a custom data source
Fixed an issue where one time payment amounts were not reflected on reports using the Payment data source until the payment was attached to an invoice
Fixed an issue where configuring a ‘Between’ operator on a report filter along with the 'Prompt User for Value' setting only resulted in the user being prompted for one value when accessing the report
Fixed a Countries screen configuration issue where it was not possible to add multiple states that used the American National Standards Code (UM)
Fixed an issue where improperly formatted dates would not return a data import exception when passed into a date conversion transform
Modified AvaTax integration to limit batch tax requests to 1000 invoices in order to prevent taxation failures during invoicing
Fixed an issue where a Service Tax Category configured on a Tax Code could not be cleared
Added a 'Add New' button to the Payment Methods page in the Customer Portal so that payment methods can be added to an account without the need to make a payment
10.4.2 API Changes
Deprecated APIs:
None
Updated APIs:
v6/Invoice/Item (Get, Post, Put): Added properties Quantity and Price
v6/Invoice/Paged/Detail (Get): Added properties Quantity and Price
v6/Invoice/Paged/<Id>/Detail (Get): Added properties Quantity and Price
v6/Invoice/Item/Credit (Post): Added properties Quantity and Price
Added a trackingId for data import batches for tracking purposes. The ID is returned when calling the DataImport/Usage API
Fixed an issue where updating an account address using Account/{id} patch would fail if the state code supplied matched an existing state code in another country
New APIs:
v6/Invoice/Item/TaxAdjustment (Post):
v6/Invoice/Item/TaxAdjustment/{id} (Patch):
For additional API documentation please see the API Reference documentation on logisense.com.
...