Hi everyone, I am encountering this feedback message behavior, i came from another page and redirecting to a certain page wherein i am displaying an error feedback message, but the error were displaying twice, first is during the loading of the page, please see the screenshot below, some dta were hidden,
and then it displays the message again after page was loaded, please see the screenshot below
even if I am staying on the same page, and just refreshing the page, the behavior was still the same, anybody got an idea on why it is happening? Any recommended solution?Thanks in advance.
Hi Rence opmac ed,
Could you provide more info about that Is this your personal environment or project Environment like dev test prod ?
Thanks
Narendra Tiwari
Hi @Narendra Tiwari this is Project Dev Environment.
Thanks,Rence
Hi,
Can you check your idle time out of the application
This can be set up through Session Login Settings given in Service Center -
Service Center > Administration > Security > Application Authentication
Default Max Idle Time is 20 minutes.
Please check this period
Hi @vignesh S ,
The message I am displaying here is a customized message based on the result of the validation I applied. I'm just wondering why it is being displayed twice. Given that other feedback message didn't behave like this.
Hi ,
1 .if its on after fetch can you confirm are you using input-param of that block is used in that dataaction/ aggregate action
2. If input param was used make sure you are called that data action on at start or only on demand
Have to tried with different machine?
Hello... yes, same behavior.
I think you are calling a expectation at two times on initialize event and on render event ?
Not really sure about that, but, the validation to show this error message was placed in the OnAfterFetch. Aside from that I am not expecting it to be display or called elsewhere.
If possible to share oml or sample oml of that ?
Oh, I'm sorry I won't be able to share an oml, company policy.I could give you a glimpse of the code it is executing, here's a sample screenshot.
instead Current screen node, remove current screen and use end node, because your'e navigating to the same screen again, so the screen lifecycle even (On Ready) will trigger again and the feedback message in OnReady will be thrown.If you are using end node life cycle screen life cycle event not occur
I might have find a solution to this, I put the displaying of the error message OnReady event of the screen.