Hi @emre - I may be too late for me but why do we not have a value to pass Automation for an EDITOR WIDGET?
For Example:
When completing a Denomination Screen we need to trap the Denomination entered in Cash Out procedures. Having a value means we would only need 1 save RULE for all denominations. At he moment we would need individual RULES…
Oh I am having a “brain fade” - of course - its passed as [:CommandValue]?. I guess I was trying to trap the Editor Widget Name then our 1 RULE would be constrained by Name and only save 1 setting…
So the “magic” in the Rule comes from the Rule Constraint:
Automation Command NameContainsCO Set USD Count
The [:CommandValue] will have an integer in it representing the Count of the bill.
Then the Action saves a setting by parsing out the [:AutomationCommandName] by grabbing the last 3 characters which will be one of: 100, 50, 20, 10, 5, 1 and multiplies that number times the Count.
Ah of course @QMcKay- I was studying Ricks sample Cash Out screen but ran out of battery on the plane last night before I got to yours!!! [:AutomationCommandName] - was the key, and I have named all my AUD denominations already to use the concatenated format.
I gone 1 step further as I needed to also embed Terminal Number so I can have individual Cash Draw Balances
Thanks - think I am struggling from lack of sleep and way too much data…