Like title says, to the ticket and orders, and anything else
Close ticket action does not change any states.
However there are state changing actions within some of the following rules.
This is a very open question as someone could only answer based on default setup since the state changes will vairy on e system is customisedâŠ
My setup has most likely allow more state changes than yours with my âslim order state formattingâ sates and PMS instrargration related states. Also my switch user flow has ticket closing flow with additional temporary states.
Anyway close to get action will trigger in sequence;
Before Ticket Closing
Ticket Closing
Ticket Closed
Take a look at all your rules under these three sections to see the actions and follow the flow to see what states are changed.
By default I think from memory there is only 3 which is order status, ticket status and entity status.
On a newly opened ticket;
Orders will change from NEW to SUBMITTED
Tickets will change from NEW ORDERS to UNPAID
Entity I think changes from AVAILABLE to OCCUPIED but not so sure on that one, thatâs what I have on mine but not sure if thatâs default.
The changes to the schedule stares will depend on circumstances too due to constraints and previous state configurations.
2 Likes
Just look at the rules it shows what states in the actions. It doesnât just change random states. If the action is not in a rule then it wonât do anything.
1 Like
The Close Ticket Action does not alter any States, ever.
It does however set an internal âflagâ on the Ticket referred to as: IsClosed (values are 0 and 1 in the DB, with 0 meaning the Ticket is still open and 1 meaning the Ticket is closed).
The IsClosed flag can be used in Automation Command Mappings for the Visible and Enabled State constraints. Look at the Cancel, Gift, and Void Automation Commands as an example.
1 Like
Thx.
Have been using IsClosed flag for certain buttons to show or not in fine tuning my delivery subsystem and is now studying the properties Lock and Unlock.