Form field type. Checkbox, select, or radio variables can maintain their form field type in page properties if their <option> tagging is preserved in the PCF. To do this, specify the output method as xml (output="xml"). Variable output encoding must be turned off in the TMPL file to avoid changing the <option> nodes into plain text; to do this, use an encoding="none" attribute in the appropriate TMPL echo statement.

Applies only to type="text"

The use of this parameter on a variable node whose type is "text" will result in an input field being turned into a WYSIWYG editor that can be used by the user to define the value of a variable.

Must be used in conjunction with the "rows" parameter.

Applies only to editor="yes"

The use of this parameter on a variable node with the editor parameter set to "yes" allows control over the resulting textarea html element rows.

Applies only to type="filechooser"

The use of this parameter on a variable node whos type is "filechooser" allows for the selection of the starting browse folder.

Applies only to type="filechooser"

The use of this parameter on a variable node with a type of "filechooser" allows for the restriction of a user within a specified folder.

Applies only to type="filechooser" and path="/some/path"

The use of this parameter on a variable node whos type is "filechooser" allows for the restriction of a user within a specified folder defined by the path parameter.

The name of the variable to be used when echoing its contents into the newly-created pages. It's used by the system as an identifier for the variable, and therefore is not seen by the end-user. This parameter is, by nature, required to be defined for each variable.

The question posed to the user. It's displayed on the left side of the user's input text field. A colon (:) is automatically added to the end of this prompt. This parameter is not required, and defaults to null / not displayed.

Similar to the prompt parameter, alt gives more information about the input required in a text field. It's displayed to the right of the text box, and usually offers an example or more information. This field is not required, and defaults to null / not displayed.

Determines whether or not this particular variable is presented to the user for modification. If a variable is not displayed, the initial value defined between the <variable> tags defines the variable's contents. However, if the variable is displayed, its contents are considered a suggestion to the user, as they can change it freely.

Defines a specific number of characters the variable may contain. Anything over and the user will be alerted that the field can contain no more than "number" characters once the create button is pressed.

Determines whether or not this variable will output xml-friendly <option> elements or a comma-seperated value. This is attribute is used only in conjunction with checkbox,select, and radio variable types. The XML type is mainly used for enhanced page properties.

Because the tcf format allows for multiple files to be created and referenced, the prompt-prefix parameter helps to identify the file to which a question refers. OmniUpdate adds the prompt-prefix to each question being asked. As an example, if prompt-prefix was "New file," the user may be asked "New file overwrite if exists?"

The default name of the resulting file without file extension. Use in conjunction with extension parameter to specify file extension of resulting file.

The following example produces a file named index.pcf

The default file extension of the resulting file. Use in conjunction with filename parameter to specify file filename of resulting file.

The following example produces a file named index.pcf

Determines whether a user can fill in a filename for a new file that is being created. This is desirable except when creating a resource file for a new folder; for example, a navigation file.

Displays a drop down list of groups that the user belongs to in the new page screen and allows the user to assign new pages to one of those groups. If the display group is set to "no", the user has no control over which group the new page is assigned.

Determines whether users can overwrite existing files. By setting the value to "no", users cannot overwrite any existing pages.

Determines the file that is opened by the editor after the Template Control File is finished. This is very helpful when creating multiple files at once. If you are using the TCF to create a new section you can open the home page for a new folder after creating a series of files in that new folder.

Determines the editing group that is assigned to new files. The "*inherit*" option assigns the new page to the same group as that of the folder where the new page is located.

Determines the toolbar used for a particular page. This overrides the user's own toolbar assignment and is helpful when creating navigation files and never want the full toolbar to be used on a page, regardless of the user editing the file. The toolbar group can also be found in the editor tag. The hierarchy is users, page and then editor tag for the toolbar that will be available to an editing area.

This parameter is only necessary to override toolbar groups for pages, irrespective of user assigned toolbars.

Determines the feed to which the newly created page will belong. By default, new pages do not have an RSS feed assigned to them and this property allows the page to automatically be assigned to an RSS feed.

Allows for the population of the RSS item's title node with content provided by a TCF variable.

Allows the RSS link to be provided by a TCF variable.

Allows for the population of the RSS item's description node with content provided by a TCF variable.

Allows for the population of the RSS item's pubdate node with content provided by a TCF variable.

Allows for the population of the RSS item node with additional XML.

Allows for the population of the RSS item node with additional XML.

Allows the author of an RSS feed item to be attached to a different user.

Allows certain pages to have assigned publishers.

Allows certain pages to have assigned approvers. This is helpful for different sections of a site which require that different people approve content.

Makes new folders created by a TCF inherit the template groups from the parent folder. This is desirable when creating new folders in a section of the site which has specific templates.

If yes, pushes a file to the production server for publishing prior to editing. This is very helpful for navigation files when creating new sections.

Will set a location for new files created other than the current folder when Create New Page was clicked.

If yes, creates folders or directories if they do not exist already and must be used with the destination parameter.

Used in conjunction with the Navigation tag.

Uniquely identifies template. If prompt-prefix is omitted, the value of this parameter will be used.

If yes, creates a new page of the chosen filename after erasing any existing file of the same name.

Navigation identifier used in correspondence with the template tag's autonav parameter

Path to navigation file into which new navigation item should be rendered.

If yes, pushes a file to the production server for publishing prior to editing.

Determines the editing group that is assigned to new navigation files. The "*inherit*" option assigns the new navigation file to the same group as that of the folder where the new navigation file is located.

Same format and functionality as the option element defined in the XHTML specs

Defines an options value for user-selection in a select field.