enhancement API - Log Incident/ServiceRequest/ChangeRequest etc to spawn BPM based on supplied serviceId/catalogId

[Martyn Houghton]

As confirmed under linked post below. the current API log request nodes only spawns a BPM if you specify the the serviceId and have a default BPM set at the service level. 

With the development of the service catalog and catalog items are now available on all current request types to allow use of different BPM workflows, can the API call logic be enhanced to apply the same capability that it offers for 'Service' level requests, so that the catalog specific BPM workflow is spawned when passing both the serviceId and catalogId as parameters.

At the moment you have to undertake an additional request first of to obtain the current BPM name from the catalog before being able to call the Log api endpoint as you need to pass the BPM Name, which is not efficient. Similarly you would not want to hard code the BPM Name in your application.

Cheers

Martyn

 

 

[Gareth Cantrell]

+1 for this please!

I struggled for ages with this one before realising that either 2 calls were needed or the external system had to have the bpm name hardcoded (not an ideal scenario!)