You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the SoftLayer API to let user to cancel product. We have use case which let the customer to cancel the the item on anniversary date, then the provider can void the customer anniversary cancellation order and cancel the server immediately. For hourly bare-metal server, I use call
SoftLayer_Billing_Item.
cancelItem ( false, false, "No longer needed", "No longer needed, was testing server" ) //cancel on anniversary date,
voidCancelService() to void previous cancellatoin
cancelItem ( true, false, "No longer needed", "No longer needed, was testing server" ) to cancel immediately.
My test example is $orderId =8623619; billingId = 103903285 hourly baremetal server
I can see a ticket 28899623 is generated then void with step 1 and step 2.
The step 3 call gives an error "There was an error querying the SoftLayer API: A cancellation ticket already exists for this server. Please refer to ticket 28899623.
Please refer SoftLayer ticket # 28969957 for more information and sample php file.
Thanks.
The text was updated successfully, but these errors were encountered:
I use the SoftLayer API to let user to cancel product. We have use case which let the customer to cancel the the item on anniversary date, then the provider can void the customer anniversary cancellation order and cancel the server immediately. For hourly bare-metal server, I use call
SoftLayer_Billing_Item.
My test example is $orderId =8623619; billingId = 103903285 hourly baremetal server
I can see a ticket 28899623 is generated then void with step 1 and step 2.
The step 3 call gives an error "There was an error querying the SoftLayer API: A cancellation ticket already exists for this server. Please refer to ticket 28899623.
Please refer SoftLayer ticket # 28969957 for more information and sample php file.
Thanks.
The text was updated successfully, but these errors were encountered: