|
|
|
|
|
|
|
|
|
|
Cascading custom applications on your Domino server (continued)
If you're going to have a person-oriented application, then you've probably looked at the Public Address Book Person form as a starting point. For the purpose of this article though, I'd like to list just the minimum fields necessary to get type-ahead and addressing to work correctly.
Table B lists the fields that will need to be on the person type form in your application:
| Field Name |
Field Type |
Description |
| Type |
text, single value |
This should be a computed when composed field with a value of "Person". As this field is required in the selection formula for ALL the views named above, it's a critical field and cannot be overlooked. |
| FirstName |
text, single value |
The person's first name. You'll probably want have this as an editable field. |
| LastName |
text, single value |
The person's last name. Usually an editable field as well. |
| FullName |
names, allow multi-values |
This is also a critical field for type-ahead and addressing to work correctly. The first entry in this field is used in a large number of columns in the required views. The contents of this field are manipulated in a variety of ways (common name, abbreviated format, soundex, last name only, etc.) to perform the lookups when your users type a name into the SendTo field of email messages. You should probably have this as a computed field. |
| MailAddress |
text, single value |
This field should contain the email address of the person. If referencing someone outside of your internal Notes domain, be sure that the MailAddress field includes all of the necessary domains and gateway information to out of your internal domain and be successfully delivered to the recipient. This field too will need to be an editable field. |
Final steps: configuring your Domino server to cascade the database
If you've performed all of the steps mentioned above, then you're done with all of the application development that's necessary. The only task that remains now is to change your server and client environment to take advantage of your hard work. A simple change to the NOTES.INI for both server and clients is all that's necessary.
Once your application has been replicated to your Domino server, all that's needed to make it cascade is to add the application name to the NAMES line of the NOTES.INI file. For demonstration purposes assume the database that you need to cascade is called APPS\ROLODX.NSF. You'd modify the NOTES.INI file to have a line as shown below (appending the cascaded application after the comma):
NAMES=NAMES.NSF, APPS\ROLODX.NSF
|
For your server,s you can edit the NOTES.INI file manually or use the remote server console for the servers where you want to cascade the database, as shown in Figure C.
FIGURE C
Additional address books can be cascaded using the Remote Server Console. Click picture for a larger image.
Its worth noting that the current release of Notes, (Version 4.6x), doesn't support the setting of cascaded address books using Server Configuration documents.
[ Prev | Next ]
|
|
|
|
|
|
-- Advertisement --
AUTOMATE LOTUS NOTES USER ID MANAGEMENT
ID Manager 4.5 from HELP Software provides a new level of automaton for managing Lotus Notes IDs. ID Manager lets Lotus Notes administrators get out of the business of creating and managing user IDs. Use our ROI calculator to see how quickly ID Manager will pay for itself.
Learn more about HELP Software products |
-- Advertisement --
Six Great Tools for IBM Lotus Sametime
- Encrypted and secure, browser-based, persistent chat rooms
- Complete chat logging and auditing
- Easy-to-define IM help desk queues
- Manage buddy lists across any organization
- Integrate awareness into Microsoft Outlook
- High powered, rapid bot development tools
Visit Instant Tech for free trials and more information. |
|
|
|
|
|
|
|
|
