Inconsistency (Bug?) with custom outline entries in mail database

HCL Domino Domino Forum
1

Hi there,

here is my problem scenario:

Since V6/7 we programmatically add a custom outline entry structure at the bottom of the NotesMailOutline Outline.

The entries have mainly this functionality:

  1. when you click on them @urlOpen() is triggered and opens a web page in a new tab

  2. when there are sub-entries, the root entries are expandable

  3. The outline entries are defined as “Action” type, in order to be able to use the PostDragDrop event of the database, when you drag & drop a document on them

So: we can open a URL on click and trigger some code (and nothing else) on a document drag&drop. This did all work fine and it still works, if you do a new database with 8.02.

Problem:

========

In the new mail template something “composite” happens to the outline entries (or the navigation as a whole) on the left. The entries can still be added to the NotesMailOutline(H). But when you drag&drop a document onto an entry with sub-entries (whatever the level), an “invalid or non-existent document” error appears and the code in the postDragDrop event is not triggered. The other entries (without a sub-entry) still work as expected (Drag&Drop possible/no error/code is executed).

Analysis:

=========

As far as my understanding goes: in the new mail template the outlines in the navigation are combined with the “Notes Mail Navigator” component. What puzzles me: why is a standard design element behaviour influenced by it, so that it is inconsistent with “normal” Notes Databases?

Question:

=========

  • Is there a way to change that behaviour (I suppose the mail navigator component is a closed one)?

  • Is this a bug (I think so)?

Anyone with ideas?

C.

2

Subject: RE: Inconsistency (Bug?) with custom outline entries in mail database

Check the properties of each entry, especially the part which DB to use from

3

Subject: Outline Entry: type Action

Hi,

thanks for the response.

The outline entries are created programmatically (so no copy/paste from another db) and they are type “Action”.

I think you mean the database selection possibility, if they are type “Named element”. As far as I can see, that behaviour cannot be based on a wrong source database setting.

Additionally all other entries - without sub entries, same type, same code - work as expected.

Or am I missing something?

C.