However, a trigger behind our table executes a tsf_send_message with 'abort' = 0. This message only serves as an info message. We expected that the trigger would continue and the record would be saved.
But somehow the tsf_send_message results in a GUI message saying 'The transaction is cancelled'.
When we set the tsf_send_message to 'abort' = 1 we get a 'Transaction ended in the trigger' error. This is how I expected it to be.
In both cases the record that triggers the messages is not saved.
If I remove the 'tsf_send_message' from the trigger the record is saved and the trigger is executed correctly.
What's going on?
Best answer by Anne Buit