POST usage_service_catalogs/update
This method updates an existing usage service catalog, which is not already canceled. A single usage service catalog can be updated by each call
Resource URL
Parameters
Name | Type | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
token | String | The token retrieved from the login method | ||||||||||||
usage_service_catalog_identifier (mandatory) | Usage Service Catalog Identifier | The usage service catalog that will be updated. The allowed usage service catalog identifier fields are the following:
| ||||||||||||
name (optional) | String | The Name of the usage service catalog From CRM.COM R14.0.0, this parameter can be updated only if the usage service catalog has one version and it is not already used | ||||||||||||
alternative_code (optional) | String | The Alternative Code of the usage service catalog. If not specified then it is generated automatically based on the specified name | ||||||||||||
description (optional) | String | The Description of the usage service catalog | ||||||||||||
create_as_draft (optional) | Boolean | If set to true then the usage service catalog will be updated as draft. If set to false or not specified at all, then the usage service catalog will be updated as effective. This is applicable only if the usage service catalog that will be updated is in draft life cycle state Deprecated from CRM.COM R17.0.0 | ||||||||||||
termed_service_requirements (optional) | String | Defines the settings related to whether a termed service will be required when adding a Usage Service on a Subscription. Applicable values are:
Available from CRM.COM R13.0.0 From CRM.COM R14.0.0, DOES_NOT_REQ_TERMED_SERVICE value is not supported Deprecated from CRM.COM R16.1.0 | ||||||||||||
installed_item_requirements (optional) | String | Defines the settings related to whether a termed service will be required when adding a Usage Service on a Subscription. Applicable values are:
Available from CRM.COM R14.0.0 Deprecated from CRM.COM R16.1.0 | ||||||||||||
provisioning_provider_identifier (optional) | Provisioning Provider Identifier | The provisioning provider related with the usage service catalog that will be updated. The allowed provisioning provider identifier fields are the following:
Deprecated from CRM.COM R16.1.0 | ||||||||||||
effective_date (optional) | Date | The date that the new version of the usage service catalog will be set as effective Applicable only when the catalog is used and any attribute of the catalog other than adding a new product is updated. If not specified, then the new version's effective date will be set as the current date Available from CRM.COM R14.0.0 Deprecated from CRM.COM R17.0.0 | ||||||||||||
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 | ||||||||||||
(optional) | Set of Usage Service Catalog Validity Objects | The time periods during which the usage service catalog will be available to be used. If not specified then the usage service catalog will be always be available If no records are specified in the set then nothing will be updated. To update a record use "action" : "update". To remove a record use "action" : "remove". To add a record use "action" : "add". Different actions can be used within the same set. For example: "set": [ { "action": "update", ........... }, { "action": "remove", ........... }, { "action": "add", ........... } ] | ||||||||||||
(optional) | Set of Usage Service Catalog Validity Objects | The periods during which the usage service catalog will be available to be used. If not specified then the usage service catalog will be always be available If no records are specified in the set then nothing will be updated. To update a record use "action" : "update". To remove a record use "action" : "remove". To add a record use "action" : "add". Different actions can be used within the same set. For example: "set": [ { "action": "update", ........... }, { "action": "remove", ........... }, { "action": "add", ........... } ] If validity_set is specified, then this parameter should not be specified and vice versa Available from CRM.COM R17.0.0 | ||||||||||||
(optional) | Set of Usage Service Catalog Usage Services | The usage services offered through the usage service catalog and their rates. At least one usage service should be specified. Each usage service can be included in a usage service catalog just once. Only products classified as usage services can be specified. If no records are specified in the set then nothing will be updated. To update a record use "action" : "update". To remove a record use "action" : "remove". To add a record use "action" : "add". Different actions can be used within the same set. For example: "set": [ { "action": "update", ........... }, { "action": "remove", ........... }, { "action": "add", ........... } ] Note that usage services already included in a usage service catalog can be removed only if the usage service catalog is still draft, or if the usage service catalog is effective or not effective and there are no usage subscription services which are posted, billable and still not billed For releases prior CRM.COM R14.0.0, this parameter is mandatory |
Referred Parameters Objects Data
Restrictions
- It is mandatory to specify one of the semi-optional parameters. Only one semi-optional parameter can be specified.
Response Data
Name | Type | Description |
---|---|---|
id | String | The ID of the retrieved usage service catalog |
name | String | The Name of the retrieved usage service catalog |
alternative_code | String | The Alternative Code of the retrieved usage service catalog |
description | String | The Description of the retrieved usage service catalog |
termed_service_requirements | String | The settings related to whether a termed service will be required when adding a Usage Service on a Subscription. The supported values are the following:
Available from CRM.COM R13.0.0 From CRM.COM R14.0.0, DOES_NOT_REQ_TERMED_SERVICE value is not supported Deprecated from CRM.COM R15.0.0 |
installed_item_requirements | String | The settings related to whether an installed item will be required when adding a Usage Service on a Subscription. The supported values are the following:
Available from CRM.COM R14.0.0 Deprecated from CRM.COM R15.0.0 |
life_cycle_state | String | The life cycle state of the retrieved usage service catalog. The supported life cycle states are the following: DRAFT, EFFECTIVE, NOT_EFFECTIVE, CANCELLED From CRM.COM R15.0.0, CANCELLED is deprecated From CRM.COM R17.0.0, DRAFT is deprecated |
effective_date | Date | The Effective Date of the retrieved usage service catalog Available from CRM.COM R14.0.0 Deprecated from CRM.COM R17.0.0 |
expiration_date | Date | The Expiration Date of the retrieved usage service catalog Available from CRM.COM R14.0.0 Deprecated from CRM.COM R17.0.0 |
udf_string_1 | String | User Defined Field of type String |
udf_string_2 | String | User Defined Field of type String |
udf_string_3 | String | User Defined Field of type String |
udf_string_4 | String | User Defined Field of type String |
udf_string_5 | String | User Defined Field of type String |
udf_string_6 | String | User Defined Field of type String |
udf_string_7 | String | User Defined Field of type String |
udf_string_8 | String | User Defined Field of type String |
udf_float_1 | Float | User Defined Field of type Float |
udf_float_2 | Float | User Defined Field of type Float |
udf_float_3 | Float | User Defined Field of type Float |
udf_float_4 | Float | User Defined Field of type Float |
udf_date_1 | Date | User Defined Field of type Date |
udf_date_2 | Date | User Defined Field of type Date |
udf_date_3 | Date | User Defined Field of type Date |
udf_date_4 | Date | User Defined Field of type Date |
provisioning_provider | Provisioning Provider Object | The provisioning provider related with the retrieved usage service catalog Deprecated from CRM.COM R15.0.0 |
log_information | Log Information Object | The log information of the retrieved usage service catalog |
validity_set | Set of Usage Service Catalog Validity Objects | The time periods during which the retrieved usage service catalog is available to be used. |
validity_period_set | Set of Usage Service Catalog Validity Period Objects | The time periods during which the retrieved usage service catalog is available to be used Available from CRM.COM R17.0.0 |
Referred Objects Response Data