SubscriptionProvisionCommand
If it is configured to do so, Smile emits this message to invoke a command in another application that provisions a new feature for an existing subscription.
The values for the command and commandID parameters are specific to each service and Smile implementation. Contact Inomial for more information about these parameters.
Message header
The following table lists the parameters in the SubscriptionProvisionCommand message header.
| Parameter | Type | Values |
|---|---|---|
| sid | integer | The service ID |
| usn | string | The unique subscription ID number for the subscription |
| command | string | The provisioning command to invoke |
| commandID | integer | A parameter to the command |
| smileMessageType | string | "SubscriptionProvisionCommand" |
Message body
The message body contains the
<SubscriptionFeaturesUpdate> element and has the following format:
{http://xml.inomial.com/smile/2.xsd}SubscriptionFeaturesUpdate
Example: The <SubscriptionFeaturesUpdate> element
This example shows a SubscriptionFeaturesUpdate XML document that contains the <SubscriptionFeaturesUpdate> element. Note that the subscription is provisioned, enabled and activated.
<SubscriptionFeaturesUpdate xmlns="http://xml.inomial.com/smile/2.xsd">
<Subscription>
<USN>2142426762</USN>
<SID>170</SID>
<ServiceName>Test service 170</ServiceName>
<Parent>1000000008</Parent>
<Properties>
<Object>
<String name="username">joe@example.com</String>
<Boolean name="billPrintName">false</Boolean>
<Boolean name="streetPrintName">true</Boolean>
</Object>
</Properties>
<ProvisionStatus>Provisioned</ProvisionStatus>
<SuspendStatus>Active</SuspendStatus>
<ActivateStatus>Activated</ActivateStatus>
<EnableStatus>Enabled</EnableStatus>
</Subscription>
<ActiveFeatures/>
<PlanScheduleItems>
<PlanScheduleItem>
<PlanCode>tp170</PlanCode>
<PlanScheduleType>1</PlanScheduleType>
<Start>2012-08-08T00:00:00.000+10:00</Start>
</PlanScheduleItem>
</PlanScheduleItems>
</SubscriptionFeaturesUpdate>