Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Date:  

Installation: https://downloads.interworkscloud.net/patches/3.28.0/CloudPlatform.Patch.3.28.28.zip
You must upgrade first to 3.28.0 using the interworks.cloud installer before applying this patch

Inheritance between an “Order Custom Field” and an “Invoice Custom Field”

With this release, inheritance between orders and invoices is feasible, meaning that Invoice custom fields can inherit Order custom fields.

As a result, we have already created the custom field called “Reseller PO code“(Purchase Order Code) on the Order module which can be seen on the first page of the Storefront’s basket page where users can fill in a PO code during the creation of an order.

Consequently, when resellers receive an invoice for one or more of their orders, they are able to know and track the exact order(s) that this invoice is based on.

On this page

The custom fields can be accessed/created by navigating to BSS Setup > Sales > Orders > Custom Fields and/or BSS Setup > Billing > Invoices > Custom Fields.

For example: Resellers receive orders from their end-customers and place them in their back-office ordering system. An order gets a unique code on the external system known as ”Reseller PO code”.

When resellers login to the distributor’s storefront and place the order, they want to keep the original Reseller PO code on the order, so that they are able to track back to the original order.

What the resellers need now is to retrieve the information of Reseller PO code when they get an invoice from their distributor. Therefore, the Reseller PO code will be inherited to an invoice during:

  • the Storefront basket checkout.

  • the BSS order execution.

If multiple orders generate an invoice then their values will be displayed as comma-separated values. When invoices are generated after a renewal, cancelation, and other actions that are not immediately related to an order, the system does not display any Reseller PO code.

For more details, on how this custom field appears during a Storefront order, please check the Ordering for a new Customer page.

For More details on custom fields, please check the Customize Entities Fields page.

New Functionalities of Office 365 Import Tool

Now our BSS Import Tool for Office 365 tenants has the ability to search and import a single Microsoft tenant as well as display their Primary Domain under the designated column.

In the event that you want to prepare for import a specific Microsoft tenant instead of many Microsoft tenants, you are now able to select the second option called “Microsoft Tenant ID/ Primary Domain update". You have the option to do so by filling in either the tenant's id or their primary domain and then click the “Get Hierarchy” button for the results to appear inside the import list prior to the actual import.

For more details, please check the https://interworkscloud.atlassian.net/wiki/spaces/ICPD/pages/4661577/Bulk+Migration+of+your+Existing+Customers+Subscriptions#BulkMigrationofyourExistingCustomers%26Subscriptions-ChoiceofSingleorMultipleTenants%27Import page.

Partial Delivery of an Order Containing “Pay Per Use” (PPU) Products is now Feasible

Since inherently PPU products have quantity zero, the partial delivery of an order containing such product(s) was not possible previously, but with this improvement, PPU products are allowed to be added to an order and be partially executed.

When you order some products (including PPU products) and navigate to: Actions > Order Delivery, the PPU products will be available on the list and their Quantity will be “PPU” instead of “0“.

Improvements in Reports

There are two new improvements concerning the Reporting module for Products and Contacts in our BSS platform.

  1. The Product ID is now available in the Products Report. This field is particularly useful when you export the full product catalog using our reports and then you utilize the exported excel for updating your external ERP system. For example, since our API returns the Product ID in the invoice items, you will now also have our Product ID in the excel file to crosscheck when you import the products in your ERP.

  2. The Creator’s language is now available inside the Contacts Report. This field displays the language of each contact.

    For more details on how to create a report, please check the Create a Tabular Report page.

API V2.2

The 2.2 version of our API allows the creation of a Subscription as well as the addition of Add-ons when no Pending Invoices are present. You can utilize the following end-point to do so.

Method

Description

POST api/Subscriptions/invoiced

Creates a subscription with no pending invoices. The subscription is not provisioned and the subscription with all it’s renewals (if exist) are marked as invoiced.

POST api/Subscriptions/{subscriptionId}/addoninvoiced

Adds an addon without creating pending invoices and provisioning to the given subscription.

Resolved Issues

EXL- XXXXX

  • No labels