If we use API to close a request, what happens to the BPM?

[Berto2002]

Hi folks, any experience or theory on this please?

Use case:

• Service Manager ICF and Workflow will be used to initiate an iBridge cloud node for power Automate
• API will be then used to update the request with the results of the work
• Our automation guy wants to then continue to use API to give it closure category and properly close it

My question is how do we ensure the request becomes properly closed when closing with the API?

In my mind, the Workflow will be sat on a node (perhaps suspend, waiting for an update from the API) but then if the API changes the status to Closed and sets Resolution Test and Category, how does the BPM get officially "Completed" (End process) so it doesn't remain Suspended forever...? Perhaps there is an additional API call needed to cancel the bpmId?

[Steve Giller]

You will need to ensure that the Workflow is in a state where it will respond to changes made to the Request. Workflows and Requests, while they can be configured to affect one another, are separate entities so if, for example, the Workflow is sat at a "Wait for Category" node, changing the Request's Status will have no effect on the Workflow, only providing a Category will move the Workflow on.

From the information given it appears that waiting for a Status Change will be the logical node, although waiting for Request Resolution may also be suitable.
It really depends on what the automation is doing.