APPLICATION DESIGN


Profile forms
Profile forms are used to create special one-per-system or one-per-key documents that can be used to store configuration and other information. You create and access a profile document with @Command([EditProfileDocument]), @GetProfileField, @SetProfileField, the LotusScript method NotesDatabase GetProfileDocument, or NotesUIWorkspace EditProfile. The document is created upon first access.

Profile documents are special in several ways:


Due to the caching, profile documents should not be used where their contents change often. In particular, do not use them for sequential numbering.

You specify a profile document with one or two values: a name and an optional key. If a key is not specified, the profile is per-system, that is, shared by all users. The following types of information are often stored in such documents:


If a key is specified, it is typically the value of @UserName. Such a document is called a personal profile document. These are useful for storing:
Caching is not ordinarily an issue for personal profiles in client applications. The user reading the profile is typically the same user who updated it, so the cache is up to date.

A profile form is a regular form. The term describes how the form is used: to view and edit profile documents.

See Also