|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reusing the Web address dialog from the R5 mail template (continued)
The final format of the address dialog, referred to as the "Directory" dialog, is shown in Figure D.
FIGURE D
 
The "Directory" dialog copies selected person documents. Roll over picture for a larger image.
Instead of returning names to a field on your form, this version of the dialog will copy the "person" documents associated with the selected names from the address book into your database.
Where to get the design elements Most of the design elements can be copied from a Notes standard R5.0 mail template (mail50.ntf). Copy each the following design elements to the clipboard and paste them into your database:
Forms
The first design element for Forms is "(wAddress)". This is the dialog itself. The second design element is "Contact|Person". Copy this if you'll be using the "Directory" version of the dialog.
Agents
The design elements for Agents are "(wAddressOpen)"and "(wAddressSave)".
Script Libraries
The design element for the Script Libraries is "Common".
Views
The design element for Views is "($PeopleGroupsFlat)". This will never get used, but the dialog form requires it.
Shared Actions
The design element for Shared Actions is "Address..." Note: there are two shared actions labeled "Address...". Be sure to use the Web version, which has JavaScript in its onClick event. The wrong version has an @Command formula. The shared action "Address..." contains the JavaScript code necessary to launch the address dialog. Instead of copying the entire action element, you may copy the code and paste it into the onClick event of any button on your form.
Setting up the calling form For the address dialog to work, there must be specific fields present on your form.
For the standard email address dialog, create three fields named "SendTo," "CopyTo," and "BlindCopyTo." The field names must be capitalized as shown and each must be a "Names" field allowing multiple values. The fields should allow commas as multi-value separators.
If you'll be using the "Delegate" dialog, create a field called "Delegee." It should be a "Names" field that's single value.
For the "Group" dialog, there must be a field called "Members." It should be a "Names" field that allows multiple values. Commas should be allowed as multi-value separators.
The "Directory" dialog doesn't require any particular fields on your form.
Each of the required fields must be both visible and editable. Neither computed fields nor hidden fields can be used. If you need to have a field hidden, use the following trick:
Use pass-thru HTML to comment out the field. Then, add the necessary HTML to create a hidden HTML field of the same name. Figure E shows this for the field CopyTo.
FIGURE E
 
The Notes "CopyTo" field has been replaced by an HTML hidden field. Roll over picture for a larger image.
You may either surround the line with square brackets or make the text pass-thru HTML.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
Sophisticated Meets Simple For Document Management
Share. Control. Manage.
Documents, emails, and content in the context of how work is done.
Native to Lotus Domino. The User Experience unseen for Lotus Domino.
Do more with less. Really.
See the possibilities Docova unleashes for Lotus Domino. |
-- Advertisement --
Mark your calendar for in-depth Lotus training, May 12-14, Boston
Join experts and peers May 12-14 in Boston for educational and networking events that deliver real-world Lotus training so you can increase productivity and efficiency in your company, advance your skills, and squeeze the most from your current environment. One registration gets you into THE VIEW's Admin2010 and Lotus Developer2010.
Register by April 10 to save $200. |
|
|
|
|
|
|
|
|
|
|