profiledocument (Domino DTD)
You can create a profile document using a profile form. On the profile form, specify the field values to store in the profile document based on your design needs. You can create one document for a database or multiple documents that are differentiated by a key you specify. Profile documents are different from standard documents because they are invisible in views, they are not included in the document count for a database, and they are cached while the database containing them is open. This makes profile documents useful for storing database-wide data, such as environment variable information, or per-user data, such as user preference information. In either case, because profile documents are cached, you can quickly retrieve information stored in them.
For more information, see Profile forms.
Containment Hierarchy
Contained by: %note.types;
Contains: %note.prolog;, %note.epilog;
Syntax
<!ELEMENT profiledocument ( %note.prolog; , %note.epilog; )>
Content
%note.prolog; , %note.epilog;
Contains any of the contents of the %note.prolog; entity, followed by any of the contents of the %note.epilog; entity.
Attributes
<!ATTLIST profiledocument
name |
%string; |
#REQUIRED |
username |
%string; |
#IMPLIED |
>
name
Name of the form that functions as a profile from for creating one or more profile documents.
username
User name associated with a profile document. If you want to create a profile document for each user of a database, you specify the user name as a key upon document creation.