|
|
|
|
|
|
|
|
|
|
|
|
|
|
DOMINO WEB COMPONENTS
User Web profile documents
By Daniel Koffler
User profile documents are an essential tool if you are planning to build any serious Web application. Whether it is color schemes and style-sheets or language and timezone settings, most Web developers need a method of keeping track of individual user preferences.
My last article discussed the limitations of the built in Domino profile documents when used on the Web. I then showed you how to create global profile documents that hold preferences for an overall application or database and simulate the functionality of true Domino profile documents. This article will extend those techniques to allow you to create individual user profile documents by adding the ability for each user to select their own preferred calendar language in the Domino Web popup calendar application I introduced two articles back. Don't worry if you didn't read the first article on how to build the popup calendar, however if you want to follow along, you will need to have read the article immediately preceding this one.
Getting up to speed
For those who don't have my last article in front of them let me refresh your memories a little. We are working in a single database that now has three forms and two views. The most important forms are Calpop, which contains the code to draw the popup calendar, and CalPro, which is acting as a profile form that contains global database information on two or more languages available to the calendar, specifically the names of the supported languages and the names of the days and months in each language. Currently the database only allows one language to be used at a time and we control which one with a radio button field on the CalPro form.
User profile documents
Now let's create a simple form to hold each user's individual language selection. Create a new form called "UserPro". Create a computed-when-composed text field named "usr" and give it the formula value: @UserName. Beside the usr field create a field called "docid". The formula for this field should be: @Text(@DocumentUniqueID) and then create a last filed on this line called "SaveOptions".
FIGURE A
 
The SaveOptions field ensures only one document gets created per user. Roll over picture for a larger image.
SaveOptions is a reserved Domino field name that controls whether the field contents in an edited form will actually be saved when the save command is issued. If this field is set to "0" then no save occurs and no new document will be created. The formula for this field should be:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
PDF Conversion for Lotus Notes
Convert Lotus Notes documents to PDF for sharing, archiving or web printing.
- 1-step PDF: As easy as clicking a Lotus Notes toolbar icon
- Archive email folders or views as a self-contained PDF
- Convert any document collection into a PDF file
- Produce print-quality output from Web applications
- Client side or Server side conversion
- Doesn't require any DLL files
- LotusScript API for developers
Ready to learn more? |
-- Advertisement --
Good Practices... Better Practices... Teamstudio.
Implementing good practices in your Notes environment doesn't have to be complicated.
Teamstudio provides software and services for efficient Notes development and simple, secure administrator control. Our new website also provides users with a library of resources to help, including:
- Ready-to-implement policies for good practice development and deployment in Lotus Notes
- On-demand webinars on topics ranging from tips for better coding, to securing your applications, managing agents, and streamlining your application deployment process
- Free utilities for download to help you more more efficiently tackle several specific tasks in Notes development
Visit our library of white papers to help you take on difficult issues in your Notes environment.
Drop by our new website and take a look! |
|
|
|
|
|
|
|
|
|
|
