Field not cleared when showing error message

Question

Hello, We are encountering an issue with a task where the default procedure applies a check on a field. If the condition is met, the field is set to NULL and an error message is raised using tsf_send_message with abort = 1. The problem is that, even though the field is set to NULL in the default template before the message is executed, the UI does not reflect this change immediately. The reset only becomes visible after the user clicks on Execute task. If we execute the message with abort = 0, another issue occurs: cannot read properties of undefined (reading 'toString'). We wanted to avoid this message using abort = 1, but in this case the field reset is not applied. Do you have any idea on how to make sure reset is applied while still avoiding the above front-end error?   Thanks

Jeroen van den Belt · Accepted Answer

Hi ​@Alexandra_Dia,Please file a ticket with a reproduction for the remaining behavior if you haven’t done so already. Thank you!

Arie V · Answer

​@Alexandra_Diaare you experiencing this with the latest Universal UI?If you’re on the latest version, could you raise a ticket in TCP and include the Default logic as well as a Har file?If you’re not on the latest version, could you first install it and test again?

Sign up

Login to the Thinkwise Software Community

Scanning file for viruses.

This file cannot be downloaded