Downloads

Versions Compared

Old Version 2

changes.mady.by.user panagenda Expert

Saved on

compared with

New Version Current

changes.mady.by.user lukas thoma

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    • Adding the public names and address book to the workspace of every end user:
      Without a dynamic configuration, one MarvelClient Action would have to be created for each and every mail server.
      Using a dynamic configuration, it is just one Action that automatically adapts to every end-user’s mail server according to the current location of each user.
    • Backing up client data to a network drive into a sub-directory “operation system username” – here, too, a variable is needed.

...

Info

References can be used universally in virtually any Action and Condition in the Configuration database and are resolved PRIOR TO THE EXECUTION of an Action.
NOTE that if resolving a reference fails, the respective Action and any Action referencing this Action will NOT be executed.
Also note that ini: and env: references never fail but return an empty string ("" without quotes) if a variable is not set.

...

Examples for References

...

Placeholders are Placeholders are primarily used for generic notes.ini variables (e.g. MC_DB=%notes_homeserver%!!panagenda\panagenda.nsf) and for a handful of special Actions actions in the Configuration configuration database (e.g. Backup, Roaming , and and  Location Actionsactions).

...

Note
Placeholders are replaced when reading a corresponding notes.ini entry, respectively DURING THE EXECUTION of an Action.

...

Contrary to references if resolving a placeholder fails, the respective Action is still executed.

In the notes.ini/Notes preference file

...

Examples for Placeholders

...

Placeholders can be used in the following MC notes.ini variables:
MC_DB, MC_DB_Unavailable, MC_DB_NotResolvable, MC_WorkingDirectory, MC_NetworkDirectory, MC_ActionsXMLStubPath

Placeholder

Corresponding reference
namespace/setting
%NOTES_HOMESERVER%notes:homeserverUsed to generically point each user to her/his respective mail server for the MarvelClient Configuration database in notes.ini, e.g. MC_DB=%notes_homeserver%!!panagenda\panagenda.nsf
%LOOKUP_MAILFILE%Used to lookup a user's mailfile path in the public adressbook
(= default)
Only supported for notes.ini MC_DB and MC_DB_Unavailable
%NOTES_DATA%notes:data_directoryFull path of HCL Notes data directory
%NOTES_SHAREDDATA%notes:shareddata_directoryShared data directory
%NOTES_CLIENT%notes:client_directoryFull path of HCL Notes client directory
%OS_SYSTEM_ROOT%os:system_rootOperating system binaries directory (e.g. C:\Windows or /Applications)
%OS_SYSTEM%os:systemThe operating system folder
%OS_PROGRAM_FILES%os:program_filesOperating system program files directory
%OS_APP_DATA%os:app_dataOperating System Application Data Directory
%OS_COMMON_APP_DATA%os:common_app_dataCommon application data directory
%OS_LOCAL_APP_DATA%os:local_app_dataThe users application data directory
%OS_USER_PROFILE%os:user_profileOperating system user profile directory
%OS_TEMP%os:tempThe users temp directory
%ENV_*%env:*Replaced with the value of an operating system environment variable; available variables names and values depend on the respective target user's operating system environment.
%REGISTRY_*%registry:*For example %registry_HKEY_CURRENT_USER\Software\panagenda\subkey% will resolve the value of "subkey" in the key "HKEY_CURRENT_USER\Software\panagenda"

For Backup/Roaming keys

Placeholders are used for backup/roaming keys instead of references for two reasons

  • The action needs both the replaced and the original value (e.g. %OS_USER%) to see if a key matches a certain set
  • For backup actions that target the filesystem the keys also define the folder names, these placeholders replace character that the OS would not allow in folder/file names

Placeholder

Corresponding reference
namespace/setting
%NOTES_USER%
%NOTES_USER_ABBREVIATED%
%NOTES_USER_COMMON_NAME%		notes:user
notes:user_abbreviated
notes:user_common_name		In filesystem backup actions this often defines the folder name. To guarantee valid filesystem paths spaces are replaced with underscores, slashes with a exclamation marks
%NOTES_VERSION%notes:versione.g. 11.0.1
%NOTES_VERSION_MAJOR%notes:version_major
%OS_USER%os:userOperating system user
%OS_COMPUTER%os:computerName of host machine; replaced with "Citrix" if os:citrix=1 (also applies to other terminal server types)
%OS_COMPUTER_ORG%os:computer_orgName of host machine (Citrix server name on Citrix and alike)
%OS_DEVICE_TYPE%os:device_typethe type of the computer, e.g. IPad Air 2

%OS_USER_HASH%
%OS_COMPUTER_HASH%
%OS_COMPUTER_ORG_HASH%




Salted MD5 hash of os:user/os:computer/os:computer_org. Used in Application Usage action to anonymize data


%INI_CUSTOM_PLACEHOLDER%
%MC_CUSTOM_PLACEHOLDER%


%ini_custom_placeholder% - gets replaced by contents of ini variable MC_custom_placeholder. This variable itself may contain placeholders. %mc_custom_placeholder% - gets replaced by contents of config variable mc:custom_placeholder.

Subject to be used when so instructed by support

%DATE_FORMAT_*%
%DATE_FORMAT_*%. Y=Year (4 digits), M=Month (1..12), W=Week (00..53), D=Day (01..31). replaced string also contains format prefix to avoid overlaps. example: %DATE_FORMAT_YW% = Y2017W37

For Location actions

Placeholder

Corresponding reference
namespace/setting
%LOOKUP_MAILSERVER%notes:userdetails_mailserverThe users home/mail server in canonicalized form, e.g. CN=server/O=company
%LOOKUP_MAILLOCATION%notes:userdetails_maillocationThe full path of the mail file on the user's home server, e.g. CN=server/O=company!!mail/user.nsf
%LOOKUP_MAILLOCATION_AUTODETECT%notes:userdetails_maillocation or
notes:userdetails_mailfile_local

This will lookup the full path of the mail file according to the type of location being managed:

For locations pointing to a server mail file this will return %LOOKUP_MAILLOCATION%
For locations pointing to a local mail file replica this will return %LOOKUP_MAILFILE_LOCAL%

%LOOKUP_MAILFILE%notes:userdetails_mailfileThe path of the mail file on the user's home server, e.g. mail/user.nsf
%LOOKUP_MAILFILE_LOCAL%notes:userdetails_mailfile_localThe path of the local mail file replica, e.g. mail/user.nsf
%LOOKUP_MAILFILE_AUTODETECT%notes:userdetails_mailfile or
notes:userdetails_mailfile_local

This will lookup the path of the mail file according to the type of location being managed:

For locations pointing to the server mail file this will return %LOOKUP_MAILFILE%
For locations pointing to a local mail file replica this will return %LOOKUP_MAILFILE_LOCAL%

%LOOKUP_MAILREPID%notes:userdetails_mailrepidThe replica id, e.g. A12272D7:005F2ACB
%LOOKUP_INTERNETMAILADDRESS%notes:userdetails_internetaddressThe users mail address
%LOOKUP_SHORTNAME%notes:userdetails_shortnameThe first short name of the user



Topics


Contact Support

Visit panagenda MarvelClient on our website!