Field Trigger Script / Broswer Caching Issue?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Field Trigger Script / Broswer Caching Issue?

L2 Linker

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.

 

jboyd98_0-1646165018375.png

 

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

jboyd98_1-1646165158523.png

--------
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:
jboyd98_0-1646165018375.png

 

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

jboyd98_2-1646165399027.png

 

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

1 ACCEPTED SOLUTION

Accepted Solutions

L2 Linker

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

View solution in original post

1 REPLY 1

L2 Linker

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

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!