Simple question hopefully - does exposing the Process Events of an Entity result in slower performance of the CRUD actions of that entity? And if so, how significantly... anything to be concerned about?
Hi Nicholas,
No, as far as I know, there is no performance consequence by exposing process events.
Enabling that property will allow you to launch a process with Create / Update actions, actions which leverage behind-the-scenes on database triggers to launch the process.
Kind Regards,João
Thanks João
Will wait to hear from another person to validate your response and then mark it as the solution.
I am actually going to rephrase my answer.
There should be an impact, as a table with a trigger will not perform as well as it would without it. Logic dictates that doing something is more expensive than doing nothing, which would also explain why this property starts unchecked.
However, if you use it in a common use case that you have a BPT or a light BPT, to be launched upon creation, the performance hit should be irrelevant. If you have 100 BPTs to be launched on that, the consequence will be more noticeable.
Taking a look to database triggers documentation (for instance, this article), that's the advice, which seems logic: