Well, better UX is debatable, that depends on the prerequisite.Making the default answer configureable would be a better UX, as the overall UX would retain the possibility of accidental presses.
That solution will only be valid if the user is logging in to it’s licensed environment.F.ex if the user has a named license and is logging in on the mobile, how do we then differentiate that and a login on the webclient or smart-client?Is there any information on the mx_t table which would tell us if the user is logging in on the mobile?
I hadn’t tried that, seems like that worked! Thanks :)
I have tried to do it this way, but the script is triggered when the search screen is opened, and not when the specific request is loaded; It seems that this event is still loaded on the search screen and not specifically when the request is opened, and is applied to all requests opened from the screen.Tested with setting up an alert, and this only triggers when the search screen is opened/search is perfomed, and twice when going back from a request screen to the search.On FSM6 U13.
As stated in the documentation; If you want your time commitments to be automatically expired or fulfilled, you must specify a fulfill event on the response code. I would expect that no time_commits are expired when no fulfill event is specified on the response code..
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
