eTBM 3

When any information in a case is updated, the tag service must update the auto generated tags for that case.

If there is an error in one of the automatic tags (SQL syntax error), the whole transaction (including the case operation) is rolled back.

So, it should be improved to avoid such problem.

POSSIBLE SOLUTION
1. Create one SQL execution per tag (today there is a single SQL that performs update in all automatic tags);
2. Wrap tag updating within a try-catch exception handling;
3. In case of error, register somewhere (probably the errorlog) about that error;
4. Continue execution of the other tags;

Possible problem in the solution: I think that, when a SQL execution goes wrong, the transaction is automatically rolledback, even if it is wrapped around a try-catch exception handler. Must check it.