Tab specific database functionality
Table of contents
Having a meaningful database title is important in developing a good Web application. The title usually relates to a name of a company if you are building a Web site for a company or it could be an application name.
One of the advantages of having a meaningful database title is that you can use @DbTitle to display the database title throughout your Web application. You can use the formula on the Web site header or window title. If you change the database title, the change is reflected throughout the application.
It is a good idea to have a unique window title for every form, page, or view (by using $$ViewTemplate) that you have in the database. A Web Page Tracking utility, such as Google Analytics, has an option to show the most visited pages by Window/Page Title. If you do not set the title, you must guess what the pages are by looking at the long Domino URLs.
The following table shows the detailed effects on this option (taken from the Designer Help).
If the option is selected
If the option is not selected
Display: Documents and navigators display faster because hotspot formulas are not evaluated until users click each hotspot.
Display: Documents and navigators display more slowly because the hotspot formulas are all evaluated at the display time.
Buttons: Domino doesn't generate a Submit button automatically.
To allow users to save and close a form
on the Web, you must create a button, hotspot, or action that contains these commands:
You can have multiple buttons on a form.
Buttons: Domino automatically generates a Submit button, at the bottom of the form.
If there is already one or more buttons on the form, Domino converts the first button it recognizes to a Submit button automatically and ignores all other buttons on the form.
You can have only one button, a Submit button, on a form.
@Commands: The following commands are supported on the Web:
Domino does not check the formulas before displaying pages.
@Commands: The following commands are not supported on the Web:
Domino checks the formulas before displaying pages. Actions that contain unsupported @commands or @functions are not displayed on the Web.
Require SSL connection option
The Require SSL Connection option is not selected by default. We select this option if we have a Web application that uses an SSL connection. This option ensures that any connection to the database uses SSL (HTTPS). A typical use of SSL is when your Web application accepts, for example, credit card transactions or stores confidential information, such as a Social Security Number or salary information.
The administrator can also set SSL by using either Internet site documents or a server document in the Domino Directory.
Don't allow URL open option
The Don't allow URL open option is not selected by default. If this option is selected, any URL command in the browser that uses the question mark syntax (?OpenForm, ?OpenView, etc) does not work on the database. Domino generates the following error message:
HTTP Web Server Lotus Notes Exception - You are not authorized to access that database.
This option is rarely used because Domino developers rely on the Domino URLs when building their application. However, it is useful when you are designing a Web application that uses a servlet. The servlet issues all the Domino URLs in the back end, so that the Domino server allows it to go through.
There are other techniques that we can use to prevent users from accessing certain views in a database. You can customize the $$ViewTemplate for the views with the "You are not authorized to access this section" message, or you can customize the $$ViewTemplateDefault if you have $$ViewTemplate for all the views that you display.
In order to do a full-text search by using the ?SearchView Domino URL command, the full-text index must be created. When you create a full-text index, you see the options as shown in the following Create Full-Text Index window.
The following table shows more information about each option (taken from the Designer Help).
Index attached files
Searches all documents and any attachments.
*Without filters, Search processes only the ASCII text of the attachments, and may not find all content.
*With filters, Search may be able to process other parts of the files.
- Without filters is faster than With filters but less comprehensive. Text in attachments is not highlighted.
- Attachments are located in the $FILE field in a document, though a picture of them appears in the BODY field. If you specifically search the BODY field for attachments, you won't find the information.
Index encrypted fields
Searches all words in fields, including encrypted fields.
Attention: Selecting this option compromises the security of information in encrypted fields.
Index sentence and paragraph breaks
Searches words in the same sentence or paragraph.
Enable case-sensitive searches
Searches for words by exact case match. Selecting this means that when you enter 'EXACTCASE' followed by your search terms, searches for your words exactly as you enter them.
Example: If you enter "EXACTCASE Apple" in the search box, Search does not find "apple."
Note: Selecting this option increases the size of a full-text index by 5 to 10%.
Update frequency (servers only)
Determines the frequency of automatic updates for the index. The server administrator determines the actual time or date for updating the full-text indexes of applications that use the Daily, Hourly, or Scheduled options. If you choose Immediate, the full-text index is created on the server as soon as possible.
The option applies only to server-based applications and to local replicas of server-based applications (for example, a local replica of your mail application). A local replica must have this option set to Immediate if you want the full-text index updated automatically during the replication process.
For more information about full-text searching, see Searching on Section 4.0.
In certain situations, we might need to allow deletion on our Web application. However, we want the ability to review and track the deletion before the documents are gone forever. By selecting the Allow soft deletion option, documents are deleted, but they are still available in the database for the period you specify. In order to view these deleted documents, create a view and choose Shared, contains deleted documents
. You can restore these deleted documents in Notes client by using the @UndeleteDocument formula.
This is not a good solution if your company needs to comply with a certain regulations, such as Sarbanes-Oxley document retention. Having a good archive and restore process is a more appropriate solution.