PROBLEM: Outline Issue: Computed outline entry will not open viewAfter migrating our application to Notes 851 we are finding that any outline entries that perform a computed action do not work correctly
Note: We are trying to use Java views.
IMPACT: SEVERE
This problem is preventing us from successfully migrating our application to notes 8.51.
WHAT WE NEED:
We hope to understand why this issue is occurring and if there are any current workarounds that are possible to enable us to migrate our application to work in the R8.51 mail template.
DETAILS:
During our code migration from our current application, based on R6.5 Mail template, to the Vanilla Lotus Notes Mail Template (R8.51) we have encountered a serious issue with the Mail Navigator (Outline).
Current Functionality - Works fine in 8.51 client with 6.5 Mail template:
In the current version of our application, which is based on a pre-Notes 8 mail template, we have a number of outline entries that have computed actions
-
We add specific code to the entry source so that our destination is computed. Here is an example of an Outline entry
-
This code will execute whenever the entry is selected. Fairly standard stuff.
@SetTargetFrame(“NotesView”);
@Command([OpenPage]; “EmbedTest”)
- This works in the current version of eProductivity, and the correct page is loaded into the central frame (Frame name = “NotesView”)
HERE IS THE PROBLEM WE ENCOUNTER WHEN USING 8.51 MAIL TEMPLATE ON 8.51 CLIENT:
-
This same behaviour is not seen when we migrate our codebase to the current Lotus Notes Mail Template.
-
When we attempt to open the page in the frame nothing happens. The current object in the “NotesView” frame is not replaced
-
In addition, if we specifically place “NotesView” in the Frame property above the page is opened, but in a new tab.
-
If we point the entry specifically to a Named Element (the page for example) then it will open correctly in the central “NotesView” frame
-
We are seeking a better understanding of how we can have computed outline entries function correctly and place our content in the central “NotesView” frame