Triggers system: Difference between revisions

Triggers system (view source)

3 bytes added , 3 years ago

m

no edit summary

109

edits

Revision as of 12:58, 24 October 2023 (view source) Priojk (talk \| contribs) mNo edit summary Tag: 2017 source edit ← Older edit		Revision as of 12:59, 24 October 2023 (view source) Priojk (talk \| contribs) mNo edit summary Tag: 2017 source edit Newer edit →
Line 156:		Line 156:

	The rule is to have only 1 trigger call per business CRUD event, even when several actions are done in the same transaction.		The rule is to have only 1 trigger call per business CRUD event, even when several actions are done in the same transaction.
	As an example: When a new ticket is created with an already assigned user, only the TICKET_CREATE trigger is called, not additionally the TICKET_ASSIGNED trigger. It is job of the trigger to intercept also this case to scan if an ~~assignement~~ is done directly during creation and to execute its custom code.		As an example: When a new ticket is created with an already assigned user, only the TICKET_CREATE trigger is called, not additionally the TICKET_ASSIGNED trigger. It is the job of the trigger to intercept also this case to scan if an assignment is done directly during creation and to execute its custom code.