2 of 2 people found this helpful
serviceRequestID and contractLineID are both optional. You can trigger provisioning without both of them.
Thanks for your reply Manish!
I am able to trigger the provisioning without serviceRequestID and ContractLineID. So, how do we associate SR number to the SOIs provisioned using API? Is there any workaround for this?
And, for the provisioning initiated through APIs, there is no cloud task record created and hence I am not able to see the provisioning task in the "Activities" tab in portal. Is there any workaround for this?
1 of 1 people found this helpful
ContractLine will be created from SOI to ServiceOffering automatically by the REST API. So not sure why you would want to create new contractline and specify to REST API.
With CLM 4.1, if you want to associated sevicerequest to an SOI, then to my knowledge you would need to use AR API to connect to Enterprise AR and create SRM ticket.
With CLM 4.5 onwards, support for handling creation of servicerequest is OOTB. You would however, need to use different REST APIs ... e.g. Cart.* or ServiceRequest.*.
It is a known limitation of CLM till v4.6.03 that REST APIs don't populate activity logs. The way to debug/troubleshoot REST APIs is using csm.log messages. Support for having REST API populate activity log is coming soon post v4.6.03 .. in one of the feature packs I believe. But still that support won't be ported back in v4.1 and that support will populate log entry in a different class ... not cloud task.
I'm using CLM 4.6 and facing the similar requierement. At the moment I trying to figure out the correct API call syntax.
Could you send me an example of your REST call?
Thanks in advance...
If I may suggest ... you can use CLM Python SDK to perform actions. It should be easier compared to forming REST API payloads yourself.
Another use of CLM Python SDK will be if you execute the command through your dev machine by putting SDK in debug mode ... you will give precise request payload in SDK log. You can then use it to form REST API payload in your program or routine. Just a disclaimer over there is ... the request payloads tend to change based on specific scenarios and inputs in your specific scenario hence the suggestion to use SDK directly in place of REST API.
thanks for your answer. Although the RESTful API is not well documented (no examples or detailed description what each class and operation is used for) I'm want (have to) use the REST API. So, If you have any more detailed docs or few examples how to use the REST API that would be really good.
Honestly the biggest issue at the moment is the syntax. How we can hand over parameters and in what JSON syntax and format CLM expect it.
Thanks in advance
The CLM 3.1 docs have an example json for the serviceofferinginstance bulkcreate request:
"So, If you have any more detailed docs or few examples how to use the REST API that would be really good.
Honestly the biggest issue at the moment is the syntax. How we can hand over parameters and in what JSON syntax and format CLM expect it."
To my knowledge there is no plan to have more documentation around REST API. Besides that I doubt whether more documentation of syntax will really ease your job.
We are pushing SDK to easily integrate with CLM. Requesting you to switch to SDK.