There are several notes.ini variables that can be set to change the behavior of the Advanced Document Properties plugin:
|AdvProp_MenuVisible||1||0, 1||If this value is 1 (default) the Advanced Properties menu will be visible. Set this to 0 to hide the entire menu and all submenus.|
|AdvProp_MenuVisibleInMailView||1||0,1||If this value is 1 (default) the Advanced Properties menu will be visible in the right-click menu in folders and views in the mail database. Set this to 0 to hide the entire menu and all submenus in this situation. This does not affect the top-level menus, and it only affects right-click behavior in mail views.|
|AdvProp_ProfileMenuVisible||1||0, 1||If this value is 1 (default) the Profile Documents menu will be visible. Set this to 0 to hide the Profile Documents menu.|
|AdvProp_ProfileShowAll||0||0, 1||If this value is 0 (default) only public profile documents and profile documents with the current user's name as a key will be available for deleting or viewing. Set this to 1 to list all profile documents, including documents that are assigned to other users.|
|AdvProp_CompareLaterMenuVisible||1||0, 1||If this value is 1 (default) the Compare Later and Compare With 'Compare Later' menus will be visible. Set this to 0 to hide these menus.|
|AdvProp_ProfileAllowDelete||0||0,1||If this value is 0 (default) the Delete button on the Profile Document list dialog will be hidden. Set this to 1 to display the Delete button on the dialog, which allows you to delete a selected profile document in the list.|
|AdvProp_HotkeyEnabled||1||0,1||Version 12.0.8 and higher: If this value is 1 (default) the CTRL-ALT-L key combination (CMD-ALT-L on MacOS) can be used to launch a Document Properties dialog when a document is the current selection. Setting this to 0 will disable the hotkey.|
|AdvProp_NoPro||0||0,1||Version 12.0.9 and higher: If this value is 1, the extra features of Document Properties Pro will not be enabled when it is installed; administrators can push this setting out to prevent users from using Pro.|
How do I know if this plugin is installed?
Choose the top-level menu item Help - About HCL Notes, and from the help dialog click the "Installation Details" button. From here, you can go to the "Plug-ins" tab. If the plugin is installed, it should be listed as "panagenda Document Properties". This is also the easiest way to determine which version of the plugin you have.
Where can I get support?
Support for this plugin is handled by HCL support, and is limited to the versions of the plugin that come pre-installed with Notes.
Can I submit feature requests?
If you have ideas or feature requests, you can submit them to the HCL Notes Ideas Portal or tweet us @panagenda.
Sometimes when I right-click a document in a view, the Advanced Properties dialog doesn't appear.
This can happen if the view doesn't have focus. Every once in a while, the Notes client will keep focus on something else – like the sidebar, or a navigator, or a toolbar – and the Advanced menu will be hidden. Often you can fix this by switching to a different tab and switching back, or selecting a different document and then trying again.
If the Advanced Properties menu doesn't appear for ANY view, make sure the AdvProp_MenuVisible=0 setting hasn't been set in notes.ini, and also make sure the plugin is installed properly using the "How do I know if this plugin is installed?" troubleshooting step above.
The Document Properties dialog doesn't work in local databases that are not in my Data directory.
This is a known issue, and we currently don't have a good workaround for it.
Sometimes if you open the database properties dialog of the local database, the Document Properties will start working for the duration of that Notes client session, but this isn't guaranteed to work.
Sometimes the field size reported by Advanced Document Properties is slightly different than the field size reported by the native document properties dialog.
The Advanced Document Properties dialog gets field sizes using the standard Notes API call for NotesItem.GetValueLength(). If this is different than the size reported by the native document properties dialog, it's usually because the native dialog also includes the item headers in the field size.
Computed for Display (temporary) fields are not shown in the Advanced Document Properties field list.
If you activate the Advanced Document Properties dialog from a view, the computed fields are not shown.
If you activate the Advanced Document Properties dialog while a document is currently open in a tab, it will normally display the computed fields along with the stored fields. Sometimes this does not work properly for MIME/Internet email documents. This is a known problem and we currently don't have a good workaround.
For Internet mail documents, why does the native document properties dialog display the Body field as multiple MIME fields, and Advanced Document Properties display it as a single rich text field?
This was a design decision we made because we felt that the converted rich text was more human-readable, and much closer to what you see when you actually open the document. It also makes it easier to search and display the field value.
If you really want to see the MIME fields of an Internet email document in all their glory, the easiest way is to drag the mail document from your inbox to your Windows or Mac desktop; by default, this will save the mail in .eml format, which is a text document containing the entire email in MIME format.
Can I update the version of Document Properties in Notes 12.0.1 or higher?
We do not support updating the Document Properties plugin in any Notes client that comes with the plugin pre-installed. This is because Notes 12.0.1 and higher has the plugin installed in the framework directory, which is normally protected from user modifications.
Even if you install Document Properties Pro, it will still use the pre-installed version of Document Properties for basic functionality on Notes 12.0.1 and higher. However, the Document Properties plugin will get upgraded with some Notes fixpacks and new releases, so in some cases you can update Document Properties by simply updating your client!