Search Engine: Elastic

Article ID: 119731, created on Jan 20, 2014, last review on May 11, 2014

  • Applies to:
  • Operations Automation

Additional WAP subscriptions

Customer has ability to purchase additional WAP subscription within single POA subscription. Wizard redirects from APS screen in Customer CP to billing screen where Change Order can be placed and paid.

It is done with help of APS application 'PBA'. This application has single resource 'Billing' which should be included into the Service Template for WAP. Instance of the PBA application has single parameter "Application API end-point URI". It points to PBA RESTful API which is listening on port 5643.

There are 3 attributes on PBA side:

  • aps_limits_notification
  • aps_upsell_returnView
  • aps_upsel_returnViewResourceId

These attributes are applicable to order. When customer purchase additional WAP subscription these parameters are passed to Change Order.

Provisioning of included resources

By default provisioning of included resources are done via 2 API calls to POA. The first call is for setting up the base limit. The second call is for setting up limit for included resource. Such behaviour is not suitable for WAP application. Limits for the resource should be set via single API call. It is necessary to enable feature 'FEA_SetResourcesInOneCall' to achieve it.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF