This document, the first in a series of four, describes in detail the design features and behavior of the Lotus Notes/Domino Out of Office functionality, answering these questions: 1. Out of Office terminology: What are some frequently used terms to describe the Out of Office functionality? 2. What does it do (and not do)? 3. Where is the Out of Office functionality located? 4. How does a Hide When formula affect when you see the Out of Office options in the Notes client? 5. How does the Out of Office functionality work? –What happens when you click the Enable button? –What happens each time the Out of Office agent runs? 6. How does the Out of Office functionality work with local replicas?
The access level that a mail file owner has in the Access Control List (ACL) of his or her mail database impacts the configuration and behavior of the Out of Office functionality in Lotus Notes/Domino. This document, the second in a series of four, describes the Out of Office functionality with respect to each allowable database access level, examining the LotusScript code differences among the following: –Manager access –Designer access –Editor access (available with Notes/Domino version 6.0)
For the Out of Office feature to work properly, certain settings in the Server document and Notes databases must be configured. This document, the third in a series of four, describes in detail all the settings necessary to configure the Lotus Notes/Domino Out of Office, relative to each ACL access level. This document, intended for Domino administrators, is a checklist of all these necessary configuration settings.
This document, the final of a series of four, describes the Out of Office feature with respect to the Domino Web Access (formerly iNotes Web Access) client, outlining the basic differences between using the feature when in the Notes client as opposed to a Web browser.