addedValuesDocs

 
Home

Variables

Forms

Reports

Queries

Groups

Globals

Preferences

Triggers

Updaters

Audit Tables

Timed Tasks

Import

Export

Remote Search

Tropes

Help

Macros

Report a Bug

 
 

addedValue Editing Form RPHdemo

Use this page to construct and modify a template for the form RPHdemo.
This is a 3 stage process of picking some of the variables you have defined, optionally editing their representation in the form and optionally changing how the form is laid out.

Choosing Form Variables

Revert to:   discarding saved version

Determine what variables appear in your form as follows.

  • Include variables in form RPHdemo by highlighting on the left and clicking ">>>".
  • Cancel inclusion in RPHdemo by highlighting on the right and clicking "<<<".
  • Order on the right matters - it's the order elements will appear in the form by default.
  • Display only variables within groups by selecting from left top dropdown menu and clicking "Set". You will not see a menu if no groups are defined.
Operation 1. Form Element

Adjusting Variable Rendering

Variables may have alternate renderings. You can choose one here, for each variable in your form. Each variable which appears in the form has been assigned a default rendering, if it is satisfactory you don't need to do anything.

Repeat the following steps for each variable you want to change renderings.

  1. Display alternate renderings by selecting one variable from the menu in the left column and and clicking 'Set Variable'.
  2. Select a rendering for the currently displayed variable by checking the radio button next to the chosen rendering.
  3. Apply the change to the form by clicking the 'Set Rendering' button.
1. Form Element 2. Alternates 3. Rendering options
Rendering sample

No HTML (RPHdemoSpeakers)[]
checkboxes
No eligible globals for labels Sorted? items per row
Mr Mrs
Ms Sir
computed menu
Multibox Size  disabled Default
This rendering failed because no query was selected..
custom
per row x height
The form RPHdemo has no on submit postprocessor
dropbox limited
Multibox Size
No eligible globals for labels Sorted?  disabled Default
password
per row
radiomenu
No eligible globals for labels Sorted? items per row
Mr Mrs
Ms Sir
textbox
per row  x  rows x cols
textList
 x  rows x cols delimiter
Required Disable ISO Filter
id  tabindex  accesskey 
class  style  lang  dir 
Show Javascript event handlers
 

 

Laying out your form

Alter the look and feel of your form here. You can use almost any HTML tags including CSS, as long as it is legal between a form tag and a close form tag, excluding input and textarea tags. HTML for these form elements - the rendering - is built by addedValues at the point in the text where you place pseudomacro calls such as [[rphdemopicture]].

Multiple valued variables may be rendered in 2 ways. The default is to have addedValues handle the layout of the multiple values; for unordered variables this is the only possibility. For ordered variables you may choose to layout seperately , which means you say where the form element for each value appears, as in [[variable-name[subscript-value]]]. You must reference each possible subscript value in the layout text.

To assign a fixed value to a variable from this form, use

  • [[variable hidden(an expression)]] - insert a hidden value for variable in the form, forcing the variables value to be expression. For example [[template hidden("fancy")]]

In a search form only, to search a variable for the same value entered for another , use

  • [[variable shadows("variable2")]] - the form will submit the same value for variable, as is entered for variable2. For example [[body shadows("subject")]]

Every form is also a report.

If a variable is not picked as one of the variables to include in the form, but is eligible to be, then the current value of variable can be used as if the form were a report. For example, if the form updates an existing message, the value of a variable you do not want changed can still be displayed to the user. Rule of thumb, variable in left of Pick variables above means it can be used in 'report mode', if it appears on the right it contributes to the form and the value can be changed.

The error report template determines how addedValues "flags" fields whose value didn't pass validation. The { formField} macro locates the formfield. Two other macros can be used to highlight the problematical form element.

  • {errorFlag(p1, p2)} - returns its first parameter if the field fails validation, the second if it is error free.
  • { formFieldErrorText()} - returns an text describing the failure, or an empty string

The formErrortext macro reports all errors together and a call to it may be inserted into the form layout. For example, {addedValueMacros.formErrorText("RPHdemo")}
The myPrefsLink macro returns a link to a page where members can change their preferences, especially whether they want forms with wysiwyg editing enabled or not. For example, {addedValueMacros.myPrefsLink("my Prefs")}

Click on RPHdemo to view your current layout.

Error report template applies to each form element in your layout

RPHdemo Additional eligible variables for the layout



Create your own Manila site in minutes. Everyone's doing it!