State machine - creating a ticket

Attributes

For more information about ticket and ticketEvent collection : see here

A ticket has its own information, but should be overall seen has a container, that includes (at least) 1 or more ticketEvent.s

The following state machine presents a ticket creation process :

DRAFT :
- the ticket is not yet confimed (= saved) by the end-user, but anyway an id is given to it.
- Once created in draft mode, a ticketEvent must be created and linked to the ticket (initial ticketEvent). The default catalogValue type for the first event is "creation"
- at this stage, the user can decide to cancel the ticket. In this case, both the ticketEvent and the Ticket are deleted.
OPEN :
- when the user confirms the ticket, the ticket transitions from DRAFT to OPEN state, and received a unique easyId (serial). For more information about numering easyId, see chapter attribute dictionnary / attribute specifications / chrono numbering here
- Once in OPEN state, 2 different actions can be executed :
  - PATCH : action that allows to change informations of the ticket : priority, person.s, part.s, contract.s ...
  - CLOSE : a ticket can be closed
CLOSED : once closed a ticket may be re-open
ARCHIVED : a ticket can be archived, meaning no more action will be applicable to it.

Ticket creation