a
aalkurd
We have built a custom online booking scheduler and successfully integrated it with the ISN REST API using the recommended
controls-v2
structure.
We are currently facing an issue with controls of type
TriggeredDropDown
(e.g., our Utility dropdowns like ID 152/Water, ID 153/Gas, ID 10/Electricity).
When we update these controls using the REST API's
controls-v2
array (for example, sending
{"id": 152, "value": "Yes"}
), the REST API successfully saves the value in the database and returns it correctly when we fetch the order details via GET. However, in the ISN Order Bravo User Interface, the checkbox trigger for these controls remains unchecked, which causes the dropdown selection to appear empty or hidden to our office team.
To work around this, we are currently forced to emulate a web browser session to log in to goisn.net and POST the raw form fields (e.g.,
obtdd152=true
,
obtdd152chk=true
,
obtdd152val=Yes
) directly to
/order-bravo/update
.
Could you please update the REST API (
controls-v2
/
OrderControlEntry
schema) to either:
  1. Automatically set the active/checkbox trigger state to true when a valid dropdown
    value
    is sent for a
    TriggeredDropDown
    control.
  2. Or expand the REST
    OrderControlEntry
    schema to accept a
    chk
    or
    checked
    boolean parameter (similar to the UI form's
    obtddXXXchk
    field) so we can activate the trigger checkbox directly.
This would allow us to completely retire our web session login workarounds and rely entirely on the official developer REST API.
Thank you!