08-11-2021, 06:06 PM
This completely depends on the action that caused the trigger to be called, because it controls the action that occur in the interface.
Usually, what happens is that a UI element from a user action causes a callback to the server to occur. This callback handles some actions which may cause a trigger to be called.
So, the UI element calls an callback, generally like this:
server.p_execute_cmd( cbk, kwargs )
.then( ret => {
// handle success
} )
.catch( e => {
// handle error
spt.alert("Error: " + e);
} )
So depending on what the cbk does (either ret or eror handling), the UI will determine what the user sees. The default behavior is that an exception will have the above.
If it is your own button, then you can handle it anyway you wish. If it is a preexisting TACTIC button, then that can get a little more complicated, depending on which one is actually being used to call the callback.
Usually, what happens is that a UI element from a user action causes a callback to the server to occur. This callback handles some actions which may cause a trigger to be called.
So, the UI element calls an callback, generally like this:
server.p_execute_cmd( cbk, kwargs )
.then( ret => {
// handle success
} )
.catch( e => {
// handle error
spt.alert("Error: " + e);
} )
So depending on what the cbk does (either ret or eror handling), the UI will determine what the user sees. The default behavior is that an exception will have the above.
If it is your own button, then you can handle it anyway you wish. If it is a preexisting TACTIC button, then that can get a little more complicated, depending on which one is actually being used to call the callback.