| Tip |
|---|
Available from CRM.COM R13.0.0 |
| Excerpt |
|---|
This method amends a subscription by adding and distributing new services or physical goods, removing existing services or physical goods or changing the distribution of existing services or physical goods. Only one subscription can be amended through each call but multiple services or physical goods can be amended through each call |
...
Name | Type | Description | ||||||||
token | String | The token retrieved from the login method | ||||||||
subscription_identifier (semi-optional) | Subscription identifier | The subscription to be modified. The allowed subscription identifier fields are the following:
| ||||||||
accounts_receivable_identifier (semi-optional) | Accounts Receivable Identifier | The accounts receivable identifier that can be used to perform the subscription modification. The allowed accounts receivable identifier fields are the following:
| ||||||||
action_type_identifier (optional) | Subscription action type identifier | The action type that should be used. The allowed subscription action type identifier fields are the following:
| ||||||||
sub_action_type_identifier (optional) | Subscription sub action type identifier | The sub action type that should be used. The allowed subscription sub action type identifier fields are the following:
| ||||||||
classification_identifier (optional) | Subscription Action Classification Identifier | The subscription action's classification. The allowed subscription action classification identifier fields are the following:
| ||||||||
payment_gateway_card_identifier (optional) | Payment Gateway Card Identifier | The payment gateway card that will be used to post a payment against the accounts receivable of the subscription. Applicable and required only for Subscriptions following the "Pay before bill" payment model. The applicable payment gateway card identifier fields are the following:
| ||||||||
performed_by_user_identifier (optional) | User identifier | The user that actually performed the action. The allowed user identifier fields are the following:
| ||||||||
performed_by_unit_identifier (optional) | Unit Identifier | The unit that performed the action. The allowed unit identifier fields are the following:
| ||||||||
performed_by_business_unit_identifier (optional) | Business Unit Identifier | The business unit that performed the action. The allowed business unit identifier fields are the following:
| ||||||||
transaction_reference_number (optional) | String | The transaction reference number for the subscription action that is performed. The transaction reference number is unique against already submitted subscription actions. | ||||||||
performed_on (optional) | Date | The date that the action was actually performed | ||||||||
billing_effective_date (optional) | Date | Determines when the subscription services that are affected by the subscription action should be billed by the billing engine. | ||||||||
billable_period_start_date (optional) | Date | Determines the start date of the billable period of each subscription service (it answers to the question “from which date should I start billing this service) that is affected by the subscription action. | ||||||||
scheduled_date (optional) | Date | The date that the action is scheduled to be executed. If not specified then the action will be executed immediately. It is important to note that if the subscription action is submitted as a scheduled one, then no installed items are specified as to also be added through this action | ||||||||
use_proposed_scheduled_date (optional) | Boolean | Defines whether the scheduled date automatically calculated and proposed by the system based on business rules, will be automatically set as the subscription's scheduled date or not. Applicable only if the subscription action includes a scheduled date and only if this scheduled date does not meet the business rules.
| ||||||||
udf_string_1 (optional) | String | User Defined Field of type String | ||||||||
udf_string_2 (optional) | String | User Defined Field of type String | ||||||||
udf_string_3 (optional) | String | User Defined Field of type String | ||||||||
udf_string_4 (optional) | String | User Defined Field of type String | ||||||||
udf_string_5 (optional) | String | User Defined Field of type String | ||||||||
udf_string_6 (optional) | String | User Defined Field of type String | ||||||||
udf_string_7 (optional) | String | User Defined Field of type String | ||||||||
udf_string_8 (optional) | String | User Defined Field of type String | ||||||||
udf_float_1 (optional) | Float | User Defined Field of type Float | ||||||||
udf_float_2 (optional) | Float | User Defined Field of type Float | ||||||||
udf_float_3 (optional) | Float | User Defined Field of type Float | ||||||||
udf_float_4 (optional) | Float | User Defined Field of type Float | ||||||||
udf_date_1 (optional) | Date | User Defined Field of type Date | ||||||||
udf_date_2 (optional) | Date | User Defined Field of type Date | ||||||||
udf_date_3 (optional) | Date | User Defined Field of type Date | ||||||||
udf_date_4 (optional) | Date | User Defined Field of type Date | ||||||||
(semi-optional) | Set of subscription services to be added objects | The services that will be added on the subscription. Those services might be either new services that should be added and distributed on the subscription or existing services that should be distributed to additional provisioning distributors | ||||||||
(semi-optional) | Set of subscription services to be removed objects | The services that will be undistributed from a specific provisioning distributor. If a service is removed from all provisioning distributors then it is also removed from the subscription | ||||||||
(semi-optional) | Set of subscription services to be swapped objects | A set of services to be swapped, along with the services that will swap them. Mandatory and additional services can be specified to be swapped. The services that will be swapped by another services.
| ||||||||
(semi-optional) | Set of subscription installed item to be added objects | The installed items that will be added on the subscription. Those installed items might be either new installed items that should be added and distributed on the subscription or existing installed items that should be distributed to additional provisioning distributors | ||||||||
(semi-optional) | Set of subscription installed item to be removed objects | The installed items that will be undistributed from a specific provisioning distributor. If an installed item is removed from all provisioning distributors then it is also removed from the subscription | ||||||||
provisioning_distributor_labels_set (optional) | Set of subscription provisioning distributor label objects | The labels that will be applied on the specified provisioning distributor for that specific subscription. Each provisioning distributor can be labeled only once per subscription. At least one service or installed item should be distributed to each provisioning distributor which is specified in that set
| ||||||||
(optional) | Set of Subscription Expenses Objects | The expenses that will be added on the subscription
| ||||||||
fields_set (optional) | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
...