<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/adv/ttadv3101s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Form Fields (ttadv3101s000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to maintain the <Link href="/baanerp/tt/glossary/glossary#000000000000015" role="glossary">form</Link> fields.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph class="Default">A form field can either be a table field or a non-table field.</Paragraph>
			<Paragraph class="Default">An example of a table field is <Emphasis>tiitm001.item</Emphasis>, where <Emphasis>tiitm001</Emphasis> is the table, and <Emphasis>item</Emphasis> is a field in that table. The form field domain is automatically filled in the current session based on the table field data.</Paragraph>
			<Paragraph class="Default">You can also define a non-table field. To do this you must define it in the program script that is linked to the session for which the form is used.</Paragraph>
			<Paragraph class="Default">This program variable must be defined with the keyword <Emphasis>extern</Emphasis> in the program script. The data type of the variable must be equal to the data type defined in the form.</Paragraph>
		</GeneralSection>
	</HelpTopic>
	<Fields><FieldHelp ID="ttadv301.fldn"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Field Name</Title>
			</Header>
			<FuncDesc>Specifies the name (code) of the form field.</FuncDesc>
			<SimpleSection><Paragraph class="Default">A form field can either be a table field or a non-table field.</Paragraph>
				<Paragraph class="Default">An example of a table field is tiitm001.item, where tiitm001 is the table, and item is a field in that table. The form field domain is automatically filled in the current session based on the table field data.</Paragraph>
				<Paragraph class="Default">You can also define a non-table field. To do this, you must have defined it in the program script that is linked to the session for which the form is used.</Paragraph>
				<Paragraph class="Default">This program variable must be defined with the keyword <Emphasis>extern</Emphasis> in the program script. The data type of the variable must be equal to the data type defined in the form.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv301.elem"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Element</Title>
			</Header>
			<FuncDesc>When the form field is part of an <Link href="/baanerp/tt/glossary/glossary#000011" role="glossary">array</Link>, this field shows the element number.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.pacd"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Domain</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tt/glossary/glossary#000000000000008" role="glossary">package</Link> code of the <Link href="/baanerp/tt/glossary/glossary#domain.tt" role="glossary">domain</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.cdom"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Domain</Title>
			</Header>
			<FuncDesc>Specifies the domain code of the form field. When the form field is a table field, this field is taken from the table definitions and cannot be modified by the user.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="desc.cdom"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Domain</Title>
			</Header>
			<FuncDesc>Specifies the description of the <Link href="/baanerp/tt/glossary/glossary#domain.tt" role="glossary">domain</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="type.cdom"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Domain Type</Title>
			</Header>
			<FuncDesc>Specifies the type of the <Link href="/baanerp/tt/glossary/glossary#domain.tt" role="glossary">domain</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.typf"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Field Type</Title>
			</Header>
			<FuncDesc>Specifies the type of the form field.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.labl"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Field Label1</Title>
			</Header>
			<FuncDesc>Specifies the label(s) of the form field description.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If you fill in a label description, it replaces the form field description. You must use labels instead of field descriptions, because the labels are translated. You can choose the related label on the form.</Paragraph>
				<Paragraph class="Default">You cannot modify this field, if the form field is table field and the form field description is the description of the table field.</Paragraph>
				<Paragraph class="Default">Enter the label code that you want to link to the form field.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="field.desc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Field Descr.</Title>
			</Header>
			<FuncDesc>Specifies the description of the form field.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.mand"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Mandatory Input</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the input on this field is mandatory.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If the field has the data type <Emphasis>byte</Emphasis>, <Emphasis>integer</Emphasis>, <Emphasis>long</Emphasis>, <Emphasis>float</Emphasis>, or <Emphasis>double</Emphasis>, mandatory input means that the value of the field must not be equal to 0. Mandatory input is an addition to the domain definition of the field. It has a higher priority than that defined at the range of the domain.</Paragraph>
				<Paragraph class="Default">The range message of the domain is given by the system, if a user leaves a field empty when input is mandatory.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>
                                    Example
                                 </SectionTitle>
				<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><TBODY><TR><TD rowspan="1" colspan="1">Field</TD>
							<TD rowspan="1" colspan="1">Employee number</TD>
							<TD rowspan="1" colspan="1">(data type long)</TD>
						</TR>
						<TR><TD rowspan="1" colspan="1">Range</TD>
							<TD rowspan="1" colspan="1">Mandatory input</TD>
							<TD rowspan="1" colspan="1">Allowed range on the field</TD>
						</TR>
						<TR><TD rowspan="1" colspan="1">$$ IN [0, 999999]</TD>
							<TD rowspan="1" colspan="1">no</TD>
							<TD rowspan="1" colspan="1">0 - 999999</TD>
						</TR>
						<TR><TD rowspan="1" colspan="1">$$ IN [0, 999999]</TD>
							<TD rowspan="1" colspan="1">yes</TD>
							<TD rowspan="1" colspan="1">1 - 999999</TD>
						</TR>
						<TR><TD rowspan="1" colspan="1">$$ IN [0, 999999]</TD>
							<TD rowspan="1" colspan="1">no</TD>
							<TD rowspan="1" colspan="1">0 - 999999</TD>
						</TR>
						<TR><TD rowspan="1" colspan="1">$$ IN [0, 999999]</TD>
							<TD rowspan="1" colspan="1">yes</TD>
							<TD rowspan="1" colspan="1">1 - 999999</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">You can only select or clear the Mandatory input check box for non-table fields. For table fields, the mandatory input is specified in the <GUIRef href="/baanerp/tt/adv/ttadv4122s000" role="session">Table Fields (ttadv4122s000)</GUIRef> session.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ttadv301.mult"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Multi-Occurrence</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the form field is a multi-occurrence field. This field can only be filled when the form type is 2 or 3.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.echo"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Echo Field</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the value of the field must be shown on the form. If this check box is cleared, the value of the field is not shown on the form. This can be a useful option for accepting a password.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.mini"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Minimum Input Length</Title>
			</Header>
			<FuncDesc>specifies the minimum number of characters expected as input on the form field.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.mxdl"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">According to Domain</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the number of digits before the decimal sign is linked to the domain definition. This is the case if the form field has the database type <Emphasis>double</Emphasis> or <Emphasis>float</Emphasis>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If the form field has another database type, the maximum display length is linked to the domain definition.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv301.maxd"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">According to Domain</Title>
			</Header>
			<FuncDesc>Specifies the maximum number of digits before the decimal sign if the form field is a <Emphasis>float</Emphasis>, or <Emphasis>double</Emphasis>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If the form field is of a different database type this field indicates the maximum display length of the field.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv301.mxil"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">According to Domain</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the number of digits after the decimal sign is linked to the domain definition. This is the case if the form field has database type <Emphasis>double</Emphasis>, or <Emphasis>float</Emphasis>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If the form field has database type, string this field indicates whether the maximum input length is linked to the domain definition.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv301.maxi"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">According to Domain</Title>
			</Header>
			<FuncDesc>Specifies the number of digits after the decimal sign if the form field is a <Emphasis>float</Emphasis> or <Emphasis>double</Emphasis>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If the form field is of database type, string this field indicates the maximum input length of the field. This length can be greater than the display length.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv301.difl"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">According to Domain</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the display format is linked to the display format of the domain definition. This is the case if the next field will be filled with the display format of the domain. You cannot modify the display format.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.difo"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">According to Domain</Title>
			</Header>
			<FuncDesc>Specifies the display format of the form field. You can fill in the display format, if you do not want to link it to the display format of the domain of the field. You can also fill in the display format if no domain is filled at all.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The display format is filled in by default with the display format defined in the domain definition.</Paragraph>
				<List><ListIntro>The display format can be used for the data types:</ListIntro>
					<ListItem>Byte</ListItem>
					<ListItem>Integer</ListItem>
					<ListItem>Long</ListItem>
					<ListItem>Double</ListItem>
					<ListItem>Float</ListItem>
					<ListItem>String (only with digits)</ListItem>
					<ListItem>Date.</ListItem>
				</List>
				<Paragraph class="Default">Depending on the type of form field, there are three different display formats:</Paragraph>
				<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><THEAD><TR><TD rowspan="1" colspan="1">Form field type</TD>
							<TD rowspan="1" colspan="1">Display format</TD>
						</TR>
					</THEAD>
					<TBODY><TR><TD rowspan="1" colspan="1">Date</TD>
							<TD rowspan="1" colspan="1">
								<Paragraph class="Default">You can use the following display format for data type date:</Paragraph> <Paragraph class="Default"><Code>%D&lt;date format&gt;</Code> or <Code>%-n.nD&lt;date format&gt;</Code>
								</Paragraph> <Paragraph class="Default">These formats are defined in the <GUIRef href="/baanerp/tt/adv/ttadv4580m000" role="session">Date Formats (ttadv4580m000)</GUIRef> session. Refer to the <DocRef>ERP LN 6.1 Programmer's Guide</DocRef> for all options.</Paragraph> <Paragraph class="Default">For example, suppose the date format 002, defined in the <GUIRef href="/baanerp/tt/adv/ttadv4580m000" role="session">Date Formats (ttadv4580m000)</GUIRef> session, is: <Code>year/month/day</Code>. Display Format = <Code>%D002</Code>. At run time, 5 December 2005 is displayed as: 2005/12/5</Paragraph>
							</TD>
						</TR>
						<TR><TD rowspan="1" colspan="1">Double and float</TD>
							<TD rowspan="1" colspan="1">
								<Paragraph class="Default">If the data type of the form field is double or float, a special amount that is defined in the <GUIRef href="/baanerp/tt/adv/ttadv4585m000" role="session">Formats (ttadv4585m000)</GUIRef> session can be specified with the following display format:</Paragraph> <Paragraph class="Default"><Code>%A&lt;format code&gt;</Code> or <Code>%-n.nA&lt;format code&gt;</Code>.</Paragraph>
							</TD>
						</TR>
						<TR><TD rowspan="1" colspan="1">Byte, integer, long, float, double, and string</TD>
							<TD rowspan="1" colspan="1">
								<Paragraph class="Default">For these types of form fields, you can use the following special characters: <Code>Z9+-*TVD</Code>
								</Paragraph>
							</TD>
						</TR>
					</TBODY>
				</TABLE>
				<Paragraph class="Default">Refer to the <DocRef>ERP LN 6.1 Programmer's Guide</DocRef> for all options.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If a figure does not fit the display format, the field is filled with overflow characters.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ttadv301.zoom"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Zoom</Title>
			</Header>
			<FuncDesc>Specifies whether a session or a menu can be activated from this field.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.zprg"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Zoom To</Title>
			</Header>
			<FuncDesc>Specifies the code of the session or menu that can be activated from the form field.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.zret"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Zoom Return Field</Title>
			</Header>
			<FuncDesc>Specifies the name of the field in the zoom process, whose value is returned to the field in the main process.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.sttp"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Startpos.Str.</Title>
			</Header>
			<FuncDesc>When the form field is of type string, this field indicates the start position of the string in the form field (at display or input).</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttadv301.dcex"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Lang/Gen.Unit Exp.</Title>
			</Header>
			<FuncDesc>Specifies the language code.</FuncDesc>
			<SimpleSection><Paragraph class="Default">A date field can contain an expression. For example, with externally declared strings in the program script that defines the language for which the date must be displayed.</Paragraph>
				<Paragraph class="Default">If the form field is of type float or double a currency can be displayed on the field with the display format: %A&lt;currency format&gt;. This field can contain an expression that defines the currency code for which the amount is displayed. For example, US$.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>
                                    Example
                                 </SectionTitle>
				<Paragraph class="Default">Your program script contains a statement: extern string curr(3)</Paragraph>
				<Paragraph class="Default">curr = US$</Paragraph>
				<Paragraph class="Default">In the form field the Lang/Curr. Expr field can be filled in with curr.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">You can only access this field if the form field is of the type <Emphasis>float</Emphasis>, <Emphasis>double</Emphasis>, or <Emphasis>date</Emphasis>.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ttadv301.defa"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Initial Value</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the form field has a default value. You can enter the default value in the next field.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Type 1, 2, and 3 forms: The default value is shown only when a new record is added (insert mode).</Paragraph>
				<Paragraph class="Default">Type 4 forms: The default value is shown when you the user modifies the field, when the field is still empty, or by using the function SET.FIELDS.DEFAULT in your program script.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv302.inpc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Inp./Ref Expres.</Title>
			</Header>
			<FuncDesc>specifies the input condition that determines the condition for which input on the field is allowed.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Examples:</Paragraph>
				<Paragraph class="Default">tiitm001.kitm &lt;&gt; tiitm.generic Input is only allowed if the value of the field tiitm001.kitm is unequal to tiitm.generic.</Paragraph>
				<Paragraph class="Default">price &gt; 0 Input is only allowed when the value of the variable price is greater than</Paragraph>
				<Paragraph class="Default">1 Input allowed</Paragraph>
				<Paragraph class="Default">0 Input not allowed</Paragraph>
				<Paragraph class="Default">All functionality described in the section on <Emphasis>expr.compile</Emphasis> in the <DocRef>ERP LN 6.1 Programmer's Guide</DocRef> can be used.</Paragraph>
				<Paragraph class="Default">If the field is from a table other than the main table, and a reference exists between the tables, the reference field or path can be given. This is useful if the main table refers twice to the reference table.</Paragraph>
				<Paragraph class="Default">For example, if a production table refers twice to the item table and an item code is displayed it is not clear for which production table field the item must be displayed. In this field the field of the production table in question can be specified. If the reference path takes more than one step, the table fields can be specified separated by commas or colons.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>
                                    Example
                                 </SectionTitle>
				<Paragraph class="Default">1) tdsls000.item1 (reference field) 2) tdsls000.item2, tiitm001.item (reference path)</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>Variables used on these fields must be declared with the keyword EXTERN in the program script.</ListItem>
					<ListItem>You can fill in attr.input with the value <Emphasis>false</Emphasis>, in the before.input section of the field in your program script. This changes the field to a display field. It overrules the input expression.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ttadv302.cnow"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Ch.without &lt;CR&gt;</Title>
			</Header>
			<FuncDesc>The characters specified here are accepted as single characters, without pressing the &lt;Return&gt; key. To define a control character, use the sign ^ followed by the character. Example &lt;CTRL&gt;[A] must be defined as [^A].</FuncDesc>
			<SimpleSection><Paragraph class="Default">A no wait character does not affect the value of the field. The ASCII value of the entered character is put in the variable "in.ret". For example: &lt;CTRL&gt;[A] as a no wait character will fill in the variable in.ret with the value 1.</Paragraph>
				<Paragraph class="Default">You can use the variable in.ret in the on.input section of the field, to do any special action.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttadv301.cmes"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Message</Title>
			</Header>
			<FuncDesc>Specifies the code of the message that is displayed on the bottom line of the screen when the cursor is on this field.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="docu"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Tech.Documentation</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, technical documentation is available.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
