The field types that present lists of choices are: Choice list fields can be editable or computed however, most choice list fields are editable. Also, some of the interface styles have an option to "Allow multi-values" on the Field Info tab which let users select several choices in the field. If available for the interface style, you can select "Allow values not in list" on the Control tab of the Field Properties box to let users add their own words without changing the original list. Enter lists and formulas for choice fields on the Control tab of the Field Properties box. The list can be generated by a formula you enter or can be created by users who enter values. You can create fields that present users with a list of choices. Creating fields to display lists of choices.Reader and Authors fields allow you to control who can read and create documents created from a form. Use Number fields for numeric and currency data. You define the field type in the Field Properties box. The field's field type determines what type of information it can contain. Or it might describe a user action - for example, "Enter a product name." Label text might name a field - for example: To, From, Author, Subject, or Date. A field label is descriptive text you create that appears with or covers the field on the form, and helps the user understand the field. You an also create a field label outside the field. You assign a field name in the Field Properties box when you create the field. When a user opens the document, the document uses the form as a template to provide the structure for displaying the data.Ī field name is a required element. When a user fills out the information in a form and saves it, the information is saved as a document. A form provides the structure for creating and displaying documents, and documents are the design elements that store data in the database. What sets forms apart from pages is that forms can be used to collect information. Everything that can be done with a page can be done with a form. A page or form can contain the following:įorms, like pages, display information. Pages can be used anywhere in your application that you have text, graphics, or an embedded control, such as an outline, to present to the user. A page is a database design element that displays information. Pages and forms are similar in certain ways. Your Domino application can be made up of one or more Domino databases. Databases hold the data, logic, and design elements for your application. Domino databases are the containers for your application. At the minimum, your application plan should address these questions:Īll Domino® applications begin with a Domino database. Domino Designer is an integrated application development environment that lets developers and Web site designers create, manage, and deploy secure, interactive applications.īefore you begin any design work, create a plan for how users will access and use your application. To collect, store, and display text in a field, create a text field, rich text field, or rich text lite field.
Text, rich text, and rich text lite fields.A field can be used on a single form, or you can create shared fields for use in multiple forms in a database. The contents of the fields can then be displayed in documents and views or can be retrieved for use in formulas. When a user, either in a Notes® client or a Web browser, creates a form, fills out the information in the fields, and saves the form, the data in the fields is stored in an individual document. A field's field type defines the kind of information a field accepts, such as text, numbers, dates, or names. Each field stores a single type of information. You create fields on forms, subforms, or in layout regions. Welcome to the Application Design section of Domino® Designer Help.Ī field is the part of an application that collects data. IBM Domino Designer Basic User Guide and Referenceīasic product usage information and programming language reference information.