RTC Follow-Up Action aborts save action in case of exceptions
![]() Hello,
we have developed a follow-up action and have configured it to run for a "work item save".
Due to a bug in the action that lead to an exception the overall save operation was aborted (the transaction rolled back).
I was expecting that the follow-up action is totally independent of the operation that it follows-up.
We are now using RTC 6.0.4. Has this behaviour been added recently or was it always like this?
|