Database call consistency problem - causing lot of different bugs

I wouldn’t rely on states for this as states do go away ( are temporary ) once the page is closed, or the user navigates to a different page on your app…

There is a plug-in that helps with that issue “Env Variables”

I bought it a couple months ago, and only used it once and was a little unhappy I purchased it…HOWEVER, I came to a point in my app today that I needed it again and noticed the updates and it is more powerful before…

Basically it allows you to use the element on your page and it stores information just like a custom state would, but any page you place the element on it will communicate and share that information…so if the user does navigate to a different page on the app, you will not lose that information…it can also allow you to modify the data and save it to database…even do a auto bind I think

I would definitely look into it, it is only $16, so definitely in my mind worth it.

Another idea, would be to add a data field that is a Yes/No ( maybe “is_over_credit_limit” ) and use that for the conditionals etc…and use the custom states to track the number and on page load search the D.B. for the number to add to custom state with a conditional workflow event that when the custom state equals zero make a change to thing to turn the Yes/NO field to YES.