I am about implementing extensions with GenericAgents and are facing some strange inconsistencies.
I tried to identify the transaction demarcation of the Generic Agents, but could not fiddle them out.
How is the transaction handling done on Generic Agent calls?
Especially the calls from GAs to custom modules, how is the transaction processed here?
My expectation would be that the GA call is transaction demarcated itself. Means surrounded by a transaction around the call via event or scheduler. And thus all modules called by the GA are running in the same / one transaction of the GA itself (ACID for the full GA operation).
Can someone point me here to the corresponding transaction code and let me know what the principle about GAs + calling custom modules are regarding transaction?
Transaction demarcation / ACID in Generic Agents?
-
- Znuny expert
- Posts: 287
- Joined: 16 Apr 2016, 08:55
- Znuny Version: see in post
- Real Name: Hans
- Contact:
Transaction demarcation / ACID in Generic Agents?
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users
-
- Znuny expert
- Posts: 287
- Joined: 16 Apr 2016, 08:55
- Znuny Version: see in post
- Real Name: Hans
- Contact:
Re: Transaction demarcation / ACID in Generic Agents?
any hints here?
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users