I’m getting a new error that i cannot seem to troubleshoot. I have an action that triggers when a patient is flagged as discharged. Most of the action is working, but the part that blanks certain columns on discharge fails if the patient’s [Follow Up] column value is “No Follow Up”
Lemme share some screenshots that may help better explain what i am seeing. We’ll use my favorite test patient Homer Simpson
The bot keeps in mind some “value when triggering” when starting a process. I had a similar situation earlier.
I would suggest either:
use a group of actions to blanks the field you need before firing the bot (if you actually need the bot - I prefer using groups of actions when it’s possible)
use various steps in the bot (not sure that would work, but just in case)
@Aurelien i may have just stumbled across the problem. Let me talk myself through this… Here’s the trail of events that happens when a new discharge record is created:
I think this is causing a conflict since “no follow up reason” cannot be blank if the value of [Follow Up] is “No Follow Up,” and provider have only recently started marking “no follow up,” which explains why i have not seen this error before. Seems i can fix this by setting [No Follow Up Reason] to “Not Indicated” or some non-blank value, or by also resetting [Follow Up] to “Undecided” or something other than “No Follow Up”
Yes, that is what I’m trying to explain, please forgive my poor expression
What I mean is that, at every step of the process, the bot keeps in mind the value stored when triggering the initiation of the process, no matter the change brought by the bot.
Just an idea:
Would you try just changing a trigger column? Like a “+1” value for example. And set the option “can trigger other bot”.
