Correction: TaskAdminServiceImpl, not TaskAdminImpl.
Thanks for reporting this.
BAMTaskSummary needs to remain filled, because this table is used by the Dashboard application to summarize information about the process executions. So it cannot be deleted. The same for OrganizationalEntity, that contains the users for the system. The TaskData content should be deleted and I will check for that today.
Thank you for checking, that issue will be one of the good reasons that the project I'm in charge of should move to the new version.
In my particular case, our project has been originally planned and tested against v5.4 and won't use Dashboard feature even if upgraded to v6.
Is it safe not to create, or to delete BAMTaskSummary and OrganizationalEntity records in the case if Dashboard isn't used ?
One idea would be to negate BAMTaskEventListener by vetoing the class by ProcessAnnotatedType ifecycle event.
You cannot erase OrganizationalEntity for sure..
But yes you can veto the BAMTaskEventListener if you are not planning to use the Dashboard module... Just for you to know, collecting the data of the process execution is a very normal and regular practice.. As soon as you start using the engine the business users will want to see statitics about the executions.. so if you veo that listener you will end up with nothing about that.
1 of 1 people found this helpful
Extra note about OrganizationalEntity: the table shouldn't grow if the amout of users using the system doesn't grow.. you will end up having a row in that table per user and per group that is using the platform.
By the way, why do you want to erase those tables?
BAM would be a nice and important feature for newly designed systems, however in our project we already have our own external statistics facility,
with help of v5.4 NodeInstanceLog and other domain-specific entities, that's why we don't need a different implementation of the similar feature for now.
Maybe our system will be able to use bam in the future releases though.
For deletion, I would like to delete those tables to prevent row sizes from growing, so I realized from your reply that I could leave OrganizationalEntity untouched.