Tab caching in practice - several questions

Question

One of the most powerfull functions of SAP ScreenPersonas I think is Tabmerging.
However I run in several challenges, I wonder how you guys dealt with it. Asume I have a flavor that is a clean copy of transaction IW21 (create Notification) in which I cached two tabs (tab 1 Notification and tab 2 Effect) and merged them into one screen.
Compatibility with ECC Field selection - mandatory fields.
when defining one field of tab 1 in ECC (trx OIAL) as mandatory, fields originated from tab 2 only become visible after entering the mandatory fields first.
This results in strange ' dynamic' screenflow that does not contribute to user experience.
Compatibility with Warning/Error messages.
when SAP gives a error or warning on a field that originated from tab 1, all fields originated from tab 2 are hidden.
Example:
Result:
Pressing Enter only processes value of 1 tab and removes actual information entered.
When merging tabs and user enters all fields (from both tabs) and presses Enter, only the fields from 1 tab are processed.
Example: in below screenshot. Enter a value in Effect and in Functional location. When you press Enter, only Functional Location is processed and the chosen Effect field is emptied.
Are there more people facing these problems with possible solutions? I am on Personas 2.0 SP02

Answer 1

That scenario is no different in its effect than having required fields.
Essentially, both in this case and the one with the required fields, the problem stems from the fact that there is a forced / predefined sequence the processing follows which conflicts with the way how tab caching works.
Tab caching will click on each tab that's cached / merged, in order to sort of "scrape the screen" before the Personas flavor is rendered. That's the way Personas knows what elements are currently in each tab, and once that's cached, it is able to rearrange the screen contents and merge the tabs. However once you went to tab 1, this tab may have a logic in the backend transaction, doing some plausibility checks, validations, what have you. If those result in a warning or an error, Personas cannot get to the next tab without user action, and it will display the message instead. At this point, it only knows the tab 1 content, and so the fields supposed to come from tab 2 won't be visible yet.
In some cases, if there is just a warning message which would only require hitting ENTER before continuing to tab 2, you can handle this using "Additional actions" in tab caching, but the possibilities there are very limited. It can press a button, but not a script button; that doesn't work for some reason. It can also press ENTER and do a Refresh Screen. That's it.
I think if at least the full set of scripting options would be available here, that could help matters a lot - or if pressing a script button would work at least. Otherwise, if using those three options don't get you over to the next tab, you're stuck...