| Excerpt |
|---|
BSS users and operation teams can benefit from creating reports and custom notifications in order to better monitor the subscriptions' history in terms of their future requests (whenever applicable). On this page you will find the guides for creating both, via the use of the respective (future request) merge fields. |
Analysis of the Future Request Merge Fields
The merge fields that are utilized for reporting the history of Future Requests of subscriptions (wherever applicable) are the following ten.
Created: Is the date the future request was created.
Creator: Is the first name and last name of the user who created the request.
Type: Is the future request actions that will be performed, be that an increase or decrease in quantity or a cancellation.
Item: Is the subscription product name or the add-on product name.
Last Update: Is the date the future request was last updated.
Last Update by: Is the first name and last name of the user who updated the request for the last time.
Revoked on: Is the date the request was revoked.
Revoked by: Is the first name and last name of the user who requested the revocation.
Submitted via Storefront: Is the value Yes if the request was submitted from the Storefront and No if the request was not submitted from the Storefront.
Status: Is the status of the external pricing (Canceled, Pending, Completed):
Canceled(status): This status means that the future request for the subscription is currently canceled, and therefore, no execution for that request will occur.
Pending (status): This status means that the future request for the subscription is currently pending execution.
Completed (status): This status means that the future request for the subscription is completed.
| Rw ui textbox macro | ||
|---|---|---|
| ||
No Historic Levels are Kept for Merge Fields None The values of these fields is kept at a history levelcontain only the current state of actions of future requests on subscriptions and not the changes or transitions of statuses. This means that when the system reviews the values these fields have, it looks at a snapshot of the subscription’s current* status. If any of these fields is updated (during the current billing cycle or the new one), the system has no way of knowing their past values. In case of a canceled or inactive subscription, the status of the last cycle will be displayed.*As current, we mean the last renewed cycle (or the initial created cycle if there were no renewals)for example if a user has created a future request on June for a subscriptions quantity increase in order to be executed on August but the user then decided to cancel it on July, the values of the merge fields will depict only the latest/current state of the future request and not the whole transition due to the cancelation action. |
Creating Reports for Subscriptions with Future Requests
In order to create a report for subscriptions with a future request, you must choose at the 1st step of the report’s creation the Subscriptions data type, along with the checkbox Future Requests.
Then, at the 2nd step of the report’s creation, you can choose any of the ten column fields.
All ten fields are located under the Future Requests General Columns.
At the 3rd step of the report’s creation, you can specify the expected status for the field Status as illustrated below by setting the Operator as “is equal to“ and the value as “Pending“.
Creating Custom Notifications for Subscriptions with a Future Request
The above-mentioned fields, are also available as merge fields when you wish to create a custom notification for subscriptions having a future request. Therefore, in order to notify and inform a specific BSS user from your operations team, of such data, please navigate to BSS Setup >Administration > Notifications > Customer Notification Details > Subscriptions, then click on the "New Notification" button, and apply the condition as indicated in the following example.
Highlighted in green color, is the condition you can utilize for this custom notification:
Entry = "Future Requests", Field = "Status", Operator = "is equal to", Value = "Pending".
The main body of the notification email should contain inside the generic text all ten merge fields for a complete representation.
Table of Contents
| Table of Contents | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|