on 11-26-2007 5:11 AM
Hi,
I'm currently working on developing an ESS scenario for IT0573 Australia (Absences). For this scenario I've not used the FPM completely. The roadmap is as follows:
Overview -> Detail -> Review and Save -> Confirmation.
The node Detail has a sub-roadmap as follows :
Detail -> Popup1 -> Popup2.
The FPM is not used for navigation from the nodes in the sub-roadmap to Detail or Review screens.
For certain conditions, error messages have been raised from webdynpro in the Detail screen. However when I use the previous button to go to the Overview screen, the messages are still persistent.
Is there a way I can counter this issue?
Regards,
Shwetha Sekhar.
Hi Chaitanya,
I tried changing the LIFESPAN of the view to <b>when_visible</b> but even then the error messages are still persistent.
Regards,
Shwetha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chaitanya,
The clearing of the error messages is normally handled by the FPM. Since we have not used the FPM completely, the error messages tend to be persistent. Nevertheless, error messages generated from the front end are cleared. Only the ones generated from the backend are not being cleared. Is there any way to clear these messages? If yes, then where are they stored?
Even if we write the code to clear these error messages in PREVIOUS BUTTON's action, it will be like re-coding the entire FPM for our scenario. Is there any other way to do it?
Regards,
Shwetha.
Hi Shwetha
The instance of the view is not getting destroyed after/before navigation.
so change the LIFESPAN property of the view
1) Double Click on the view
2) Goto <b>PROPERTIES TAB</b>
3) In the<b> view Properties</b> Section
4) Change the LIFESPAN property to <b>when_visible</b>
Best Regards
Chaitanya.A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.