Subscriber Context Requirements

A set of accessors is provided in the Subscriber Context interfaces to easily read/write information in it.

SubscriberContext contains two Contexts: Origin and Target. Each contains zero to many typed Items. Available types are "Product", "TechnicalProduct", "Network" or "Other". At each level, you may store parameters, name with value(s), in dataset. None of these datasets has a parent. At Subscriber Context level, a collection gathers all datasets. A Collection is an object that is used in a ServiceOrder to provide access to any dataset of any ProductOrderData within a SOD. This object is linked to a SOD through the "collection" attribute.

The corresponding name in the collection is as follows:

• "ctxOrg" for dataset of Origin Context

• "ctxTrg" for dataset of Target Context

• "ctxOrg.<ItemName>" for dataset coming from Item within Origin Context

• "ctxTrg.<ItemName>" for dataset coming from Item within Target Context

When the ServiceOrder is linked with a SubscriberContext:

• parent of dataset of its ServiceOrderData is dataset of SubscriberContext

• parent of collection of its ServiceOrderData is collection of SubscriberContext

A single interface -- sodata::SubscriberContext -- allows you to manipulate items within Target/Origin Context.

The methods in the SubscriberContext interface let you add and remove items, get and set parameters from any dataset, and commit Item of Target context.

Retrieving SubscriberContext from external systems requires you to write custom code. The FrameworkService mechanism is used by Fulfillment Provisioning Catalog or any module that needs to create/retrieve the SubscriberContext based on its key (scId).

Copyright © Cloud Software Group, Inc. All rights reserved.