Wait for Custom Field Suspend node - not working as expected (moving on when value is updated)

[Berto2002]

We are testing the Suspend > Wait for Custom Field Hornbill Automation Node.

At the start of the flow, h_custom_d field is not populated.

We send off to a Cloud node and an API comes back and adds a value into Custom D.

But the workflow is not detecting this update and thus not moving on.

This is our config where the value of "Custom D" is selected from a drop-down list.

Our use case is that I need the Request to detect and be able to use a string value sent-in via API to then act upon

Note I previously added to the forum that the help file was wrong but this seems inconsequential unless there are general issues with that feature

Thanks in advance for any insight into this

[Steve Giller]

14 minutes ago, Berto2002 said:

We send off to a Cloud node and an API comes back and adds a value into Custom D.

It would probably assist the devs if they knew which API here.

[Berto2002]

@Steve Giller and others.

This one: Entity API / update (hornbill.com)

We find the links don't always work to the HB documents so it's the Request Update API:

"The customFields input parameter enables the update of any of the custom fields against your request records.

The input is of type xs:string, but the API expects a string representation of a JSON object, with key-value pairs for each custom field needing updating, where they keys are the database field names and the values are in their native datatypes. The following example, when provided as a string to the customFields input parameter, would prompt the API to update the h_custom_a, h_custom_p, h_custom_21 and h_custom_26 fields angainst the target request."

We are sending either "success" or "failure" into h_custom_d

[Berto2002]

Just wondered if we could have an update here? Any support tested this perhaps or any other customers?