Form

Workflow Manager Developer Guide

HGD_Variant
15.00
HGD_Product
GeoMedia Smart Client
HGD_Portfolio_Suite
Platform

A Form is used as a root-element for the creation of (complex) forms. The general usage is:

<Form name="ENTITYPOSITION" table="PR_ENTITYPOSITION" idfield="ID">
 <FormTab name="Tab" label="Operation symbol" >
   <FormGroup name="Group1" label="Details">
     <FormField label="ID:" name="ID" type="textfield" datatype="number" required="false" visible="false" maxlength="50" editable="true"/>
     <FormField label="Name:" name="NAME" type="textfield" datatype="string" required="false" maxlength="50" visible="form,list" />
     <FormField label="Description:" name="DESCRIPTION" type="textfield" datatype="string" required="false" maxlength="50" visible="form" />
     <FormField label="Operation:" name="OPERATION_ID" type="combobox" datatype="string" required="true" maxlength="50" lov="SQL[SELECT ID,NAME FROM PR_OPERATION]"/>
     <FormField label="Editor:" name="EDITOR" type="textfield" datatype="string" required="false" maxlength="50" visible="form,list" />
   </FormGroup>
 </FormTab>
 <FormAction name="SAVE" label="Save" action="save" />
</Form>

The possible Controller (for example: List, Form) which can be implemented is referenced in the Workflow-XML.

Form-Attributes

Attribute

Mandatory

Description

name

yes

Unique name of the form within the FormList (has to be written in UPPERCASE letters and must not contain any special characters).

<Form name="CHECKLIST" ... />

customscript

no

Definition of an external script source.

<Form ... customscript="pr/pr_unit.js" ... />

customstyle

no

Definition of an external style source. Automatically the folder Custom\Styles is choosen. So you only have to define the name of the customstyle.

<Form ... customstyle="ig-event-icons.css" ... />

editable

no

Boolean value which defines if the form is editable.

 <Form ... editable="false" ... />
 
 <Form ... editable="SCRIPT[...]" ... />
 
 <Form ... editable="SESSION[KeyExists ({SESSION.SELECTION})]" ... />
 
 <Form ... editable="SQL[SELECT CASE TYPE WHEN 'Normal' THEN 1 ELSE 0 END FROM TABLE1 WHERE ID={FORM.ID} ...]" ... />
 
 <Form ... editable="OBJECT[...]" ... />

filter

no

Indicates the WHERE-clause of the view.

<Form ... filter="SQL[INCIDENT_ID ={SESSION.INCIDENT1.RPI_ID}]" ... />

idfield

no

Defines the Primary Key column of the table used to reference the respective lines with (has to be written in UPPERCASE letters and must not contain any special characters).

<Form ... idfield="ID1" ... />

inherits

no

Defines that the form is derived from another one (has to be written in UPPERCASE letters and must not contain any special characters). This saves redundant work and should be used if similar forms are derived from a root-form.

<Form ... inherits="FORM_XY" ... />

isfilterareaopen

no

Defines if the filter area above a List-Controller should be initially open (default="false").

<Form ... isfilterareaopen="true" ... />

label

no

Label of the form.

<Form ... label="Form xy" ... />

order

no

Indicates the column to arrange the view, parameter ASC (ascending=default), and DESC (descending).

(See SQL command ORDER BY)

<Form ... order="SQL[Order By TEXT ASC]" ... />

pagesize

no

Defines the number of list lines per form. If this attribute is set, four pagination buttons (first page, previous page, next page, last page) are added automatically to the List-Controller page.

<Form ... pagesize="15" ... />

table

no

Defines the table, which is the base for your FormFields. So the value for table has to be the same as in the database.

<Form ... table="PR_CHECKLIST" ... />