Wait for custom field to be set node

[Jim]

Hi,

 

I have a process that is told to wait for custom K, this is populated by the API but the node doesn't acknowledge the update, although other custom fields do acknowledge the update via API

Could this be looked into? this is working with a supplier and the best way for us to pause our process and then progress is when we receive the relevant data from them which we populate with the API

[David Hall]

@Jim

In the most recent Service Manager update a new parameter 'resumeBpmProcess' was added to the Requests 'Update' operation as detailed here https://docs.hornbill.com/servicemanager-api-api/entities/requests/espflowcodeentityoperation/content/update

If you set this parameter to true when making the update API call it should trigger the workflow process to resume.

Kind regards,

Dave.

[Jim]

Hi @David Hall, 

 

I have tested this and it still does not progress, I have a separate flow that updates custom M without this parameter that does progress. 

When updating custom 25, or K it does not seem to progress at all with or without it and the values are definitely being set

[Jim]

This is all just test data but you can see from the config, payload and settings that its still not progressed despite data being set and resumeBpmProcess set to true

 

{ "params": { "requestId": "SR00090856", "customFields": "{\n\"h_custom_k\":\"PF47287494\",\n\"h_custom_l\":\"\",\n\"h_custom_o\" :\"PW0CXYHR\",\n\"h_custom_p\": \"SCC-001\",\n\"h_custom_25\":\"\",\n\"h_custom_26\":\"0.0\",\n\"h_custom_28\":\"1.0\",\n\"h_custom_30\":\"2.0\",\n\"h_custom_71\":\"0.0\",\n\"h_custom_72\":\"0.0\",\n\"h_custom_74\":\"0.0\",\n\"h_custom_77\":\"2024-10-23\",\n\"h_custom_80\":\"\"\n}", "h_external_ref_number": "V75748Y", "resumeBpmProcess": "true" }, "@service": "apps/com.hornbill.servicemanager/Requests", "@method": "update" }

[Gareth Cantrell]

I had a similar issue with updating a custom field from an auto task with the main workflow set to wait for custom field.

To get it working, I had to issue a timeline update as part of the custom field update, so I'm wondering if sending an "updateReqTimeline" API call immediately after sending the "update" API call will have the same effect?

[Jim]

This would make some sense in the one that works as I tell it to set the status of the request to open, as on that one was on hold, not thought about it on this one that's erroring as its already open I will test later on

[David Hall]

@Jim

Ok I'll double check that new parameter as it was working correctly when I previously tested it but I'll check with custom K to be sure.  As Gareth mentions... the updateReqTimeline should have the effect of moving on the workflow as well... this new param was added just to avoid the need to add a timeline entry.

[Jim]

Hi, 

Thanks both the update request timeline has worked and saved me from delivering some bad news  thank you 

Funnily enough it does actually make sense to update the timeline in my scenario also to show when the fields were updated and how often