Name | Type | Description |
---|---|---|
id | String | The ID of the retrieved notificationprovisioning request |
number | String | The number of the retrieved notificationprovisioning request |
type | String | A code that uniquely identifies the type of provisioning request that is performed. The supported options are the following:
|
Sequence Number | String | An auto generated number that indicates the order of sending the provisioning requestsThe sequence number of the retrieved provisioning request |
Scheduled Date | Date | The date that the provisioning request is scheduled to be send |
Executed Date | Date | The date that the provisioning request was actually send |
Priority | String | The priority of the provisioning request. The supported values are the following:
|
life_cycle_state | String | The life cycle state of the retrieved provisioning request which can be PENDING, REJECTED or COMPLETED |
Request | String | The actual request that was send to Conax |
Response | String | The actual response that was received from Conax |
Reference number | String | A reference number provided by Conax after receiving the request |
Error Code | String | The error code received by CRM.COM or Conax in case that the provisioning request was rejected |
Error Description | String | The error description received by CRM.COM or Conax in case that the provisioning request was rejected |
Process Name | String | The name of the process that submitted the provisioning request, which can be one of the following:
|
Process ID | String | The ID of the process that submitted the provisioning request (if applicable) |
Log Information Object | The log information related with the retrieved provisioning request | |
parameters_set | Set of Notification Item objects | The parameters which will be used to generate the Web Service Calls that will be send to Conax. That information differentiates based on the type of request |
Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...