The following parser statements are available in GroupWise 6.5 and later releases:
For GroupWise 6.5 and later releases, a GroupWise Administrator can turn off the ability for GroupWise to change an LDAP password. If this occurs, any attempt to call Account::SetPassword returns an error.
If the LDAP authentication is turned on AND their LDAP password has expired, the Object API normally prompts users to change their passwords. If the GroupWise Administrator has set this flag, the normal Change Password dialog appears but all text boxes are disabled, the OK button is disabled, and a new error message is displayed that asks the user to change his LDAP password using other means.
For GroupWise 6.5 and later releases, the Outbox folder was renamed to be the Sent Items folder, which causes a conflict with the current Sent Items query folder. The first time a user runs the GroupWise 6.5 code, it hides the Sent Items query folder or renames it to Sent Items Old.
If the query folder is hidden, GroupWise 6.5 displays only the new Sent Items systems folder. If the query folder is renamed, GroupWise 6.5 displays both the query folder and the new Sent Items system folder while older GroupWise Windows clients continue to show the Sent Items query folder and hide the new Sent Items system folder.
The Object API always allows access to both the query folder and the Sent Items system folder. If the two folders remain with the same name, you must use the ObjType property of the Folder object to distinguish between the two folders.
Two new filter statements are available in GroupWise GroupWise 6.5 and later releases. These statements should be added (after the SUBJECT, PLACE, and other text) to the set of available statements for text searches.
CATEGORY MATCHES "Sample"
This statement returns any item that contains a Category of name Sample.
NOTE:Only the text operation MATCHES works with the Filter expression CATEGORY. All other text operations return an error.
This statement returns any item that contains a Category of name Sample, and for which the Sample Category was marked as the Primary Category for the item.
NOTE:Only the text operation MATCHES works with the Filter expression PRIMARY_CATEGORY. All other text operations return an error.
A new filter statement is available in GroupWise GroupWise 6.5 and later releases. The statement should be added (after the ON_CALENDAR, OFFICIAL_DOCUMENT_VERSIONS_ONLY, and other text) to the third set of available statements.
This statement returns any item that has been placed on the master Checklist. If a NOT is placed before the statement, the search finds items that are not on the Checklist only.
Two new filter statements are available in GroupWise GroupWise 6.5 and later versions and should be added (as part of the CURRENT_VERSION_NUMBER, NUMBER_READ, and other text) to the set of available statements.
This keyword returns any item with a Task Priority value that matches the Numeric operation. For example, a task that displays in the GroupWise client with Task Priority A3 can be found with the following filter statements:
(TASK_PRIORITY = 3) (TASK_PRIORITY > 2)
This keyword returns any item with a Task Category value that matches the Numeric operation. For example, a task that displays in the GroupWise client with Task Priority "A3" can be found with the following filter statements:
(TASK_CATEGORY = "A") (TASK_CATEGORY < "B")
NOTE:This is a Text value sent in to a numeric operation and follows the pattern of the GroupWise client, which also searches for the Task Priority with the numeric operators =, !, >, <, etc.
The GroupWise client always displays the Task Priority as a numeric value after the Task Category letter value. The Object API, however, split the Task Priority and Task Category into two separate properties. When building a Filter or Query expression, the GroupWise Windows Client splits the shown Task Priority field into the Task Category and Task Priority fields to search. These changes to the Object API follow the GroupWise Client split for separating the two values for a Task search.
A detailed list of GroupWise error messages that appear in ConsoleOneTM, GroupWise agents, and GroupWise clients, along with possible causes and suggested actions to resolve the problem, can be found in the Troubleshooting section of the GroupWise 6.5 documentation.
For any Date field that is viewed through the Object API (including the Birthday field), note the following restrictions:
The user must be logged in using MultiLogin.
The MultiLoginAddressBookSupport (part of the Application4 object) must be set to TRUE.
If these two restrictions are not followed, Object API can display only the String fields as passed by the MAPI Address Book providers.