Field Trigger Script / Broswer Caching Issue?

jboyd98 — Tue, 01 Mar 2022 20:10:55 GMT

I have a field trigger script on dbot status changing; essentially updating a custom field to nothing if the an incident is re-opened.

if field=="dbotStatus" and old=="Closed" and new=="Active" and incidentType=="Azure Sentinel":
demisto.executeCommand("setIncident", {'customFields': {"sentinelclosereason": ""}})

This seems to work as the previous "Sentinel Close Reason" is empty after it runs.

Now when a user closes a case, they are forced to re-choose the "Sentinel Close Reason".

--------
The objective is being met above, however there's a field trigger script tied to "Sentinel Close Reason"

If the user happens to pick the previously set reason, even though they are forced to choose from the drop down it doesn't recognize it as a field change. Only if it's different from the previous sentinel version.

I noticed that even after this, where the Sentinel Close Reason value is blank after a re-open:

If I go to my browser and hit the "refresh" button, i can pull back the previous "Sentinel Close Reason"

Its like it's not being saved in the database, even though I can see an empty value in the context data after a re-open.

Any thoughts are appreciated,

Thanks,

Boyd

Re: Field Trigger Script / Broswer Caching Issue?

jboyd98 — Tue, 01 Mar 2022 20:18:54 GMT

Disregard, my re-open trigger script was set to yes for run after modification. That seems to have fixed it.

topic Re: Field Trigger Script / Broswer Caching Issue? in Cortex XSOAR Discussions

Field Trigger Script / Broswer Caching Issue?

Re: Field Trigger Script / Broswer Caching Issue?