Bug
Exception in computation rule creates unlabeled topic
Issue description
Given a topic type TT1 with a computation rule CR1. When a new instance T1 of TT1 is created and the evaluation of CR1 to compute the result for T1 throws an exception, the instance T1 is created in the store, but it is not found by searching since the label was not created. If T1 is the first instance of TT1, the index in this case shows an instance count of 1, but is otherwise empty.
Developer comments
The resulting topic in this case exists, but is otherwise not found. It is invisible or cannot be referred to. The only indication of its existence is the instance count.
This changes should do the trick: an exception in a result calculation of a computation rule is isolated and if it fails there will be no entry created in the table and the exception is just logged. On the error page of the computation rule, it will be displayed. This should suffice to tell the admin that something is not right, but the store otherworks remains functional. The user does not notice the error, which is acceptable since it is a derived secondary result of the persisted primary data.
|
Work sessions3
Start |
2024-01-27T10:01:00
|
End |
2024-01-27T11:46:39
|
Participant |
Robert Cerny
|
Start |
2024-01-27T12:38:57
|
End |
2024-01-27T13:12:44
|
Participant |
Robert Cerny
|
Start |
2024-01-28T07:22:46
|
End |
2024-01-28T07:31:29
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.