Bug #7990
investigate what can be improved after 7494a adds BlockDefinition instance to Scopeable.scopeStart
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
History
#1 Updated by Constantin Asofiei 6 months ago
With #7494, scopeStart
knows the exact BlockDefinition
instance which is notified. The same can be added to scopeFinished
.
This task is meant to investigate TransactionManager API calls from scopeStart/Finish, which are redundant as the info is already at the block parameter.
The same can be investigated for scopeDeleted
- pass the referent to avoid ProcedureManager calls?