You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
usage_service_catalog_validity parameter object data
| Name | Type | Description |
|---|
valid_date_from (semi-optional) | Date | The date that the usage service catalog will become valid |
valid_date_to (optional) | Date | The date that the usage service catalog will become invalid. This is optional as a usage service catalog can be valid for ever, starting from a specific date Applicable only if valid_date_from is specified |
valid_month_from (semi-optional, mandatory on conditions) | String | The month that the usage service catalog will become valid This field is mandatory if the valid_day_from is specified, and vice versa |
valid_month_to (optional, mandatory on conditions) | String | The month that the usage service catalog will become invalid. This is optional as a usage service catalog can be valid for ever, starting from a specific month Applicable only if valid_month_from and valid_day_from are specified This field is mandatory if the valid_day_to is specified, and vice versa |
valid_day_from (semi-optional, mandatory on conditions) | String | The day that the usage service catalog will become valid This field is mandatory if the valid_month_from is specified, and vice versa |
valid_day_to (optional, mandatory on conditions) | String | The day that the usage service catalog will become invalid. This is optional as a usage service catalog can be valid for ever, starting from a specific day Applicable only if valid_month_from and valid_day_from are specified This field is mandatory if the valid_month_to is specified, and vice versa |