This is what I am thinking about … when the GC Entity is selected, we store the Account Balance and apply the Calculation whenever we want.
When we finally do fire the Calc Action (ie. maybe in the Settle Rule), we use 3 identical Actions which are constrained by the GC Account Balance to ensure it does not get overdrawn. I do a similar thing in the GC Tutorial to ensure GC Tender does not overdraw the Account. The Automation then swaps out the GC Entity with a “dummy” Entity named ZZGCDUMMY.
So for the Ticket Entity Changed Rule, we simply store the Balance in a Local Setting, and maybe fire the first GC Calc to ensure that calculation Type has not already been applied.
I show the other GC Calcs in this screenshot as well, but they (all 3) probably should go somewhere else, like in the Settle Rule.
