That said, I am still a proponent of making function libraries and using CALL:X as @JTRTech has shown ā¦ that way, all your code is in a single place.
@pauln can you confirm I have read that right, the verdict was buttons canāt be mapped to entity state and you had to use a ticket state rather than entity state?
We know that Order States work as well, correct? I mean, Void/Cancel and Gift/Cancel buttons work on Order State.
Not sure though if AMCs are Entity State awareā¦ but not sure why they would be restricted from the State mappings. Might have to do with the fact that a Ticket can have multiple Entities assigned, so the State of which Entity Type to look at is the questionā¦
Void/Cancel etc are only valid on order line mapped buttons.
Ticket states for ticket level buttons.
So under the impression entity states arenāt mappable on a button on ticket line, well I couldnāt get it to work and makes sense following that pattern.
Entity states are not listed like ticket states which is another thing suggesting that its not possible.
Yes correct assumption @JTRTech - sorry for the delay, extremely bogged down
The issue is the MAPPINGS in my case, there is not State available for ENTITY as far as āEnabledā, āVisibleā - it is all based on Ticket.