We have a development requirement to communicate between two Web Dynpro Applications. Due to FPM navigation has the technical restriction, we cannot solve this issue.
Here are the main scenarios for this requirement:
1. Open a Web Dynpro Application 'A', which has a set of the related data to be held in ALV List
2. Open another Web Dynpro Application 'B' from 'A' to change the selected data
3. After completing the relevant changes, application 'B' needs to notify application 'A'. Application 'A' will update its own data according to results from 'B'.
When an user opens multiple applications A1, A2, A3, ..., and then it should activate application 'B' in A1, but 'B' cannot correctly identify the calling application A1 due to there are multiple application A* to exist.
My question is how to let 'B' identify the corresponding application A1.
In a word, how do application 'B' notify the calling application 'A' (like application ID or process ID)?
Can Portal Event correctly handle this situation? (correctly identify the calling application by ID?)