|
| |
| ||||||||||||||||||
|
This document just provides an introduction to rendering your customized forms to the web. For full information on this topic, see our Internet Services help.
Preparing customized standard forms
If you customize a standard form, you must also customize the form's HTML template for your web users. To do this, double-click the template, then edit the HTML code.
Preparing new forms
If you create a new form, you must also make an HTML template for it for your web users. To do this:
1 Select or open the form in FirstClass Designer.
2 Choose File > Save as HTML.
The HTML template is saved with the form ID as its name. Don't rename this template.
The HTML code in this template is just intended as a starting point. You will need to refine it manually by editing it just as you would any template for a customized standard form. Don't remove the web tags generated by FirstClass Designer.
 NoteFirstClass Designer can't convert all field types to HTML.
3 Upload this template to your server.
 TipAs an alternative, you can copy the contents of this template to a FirstClass document, name the document with the template name, and use it in place of the template. This simplifies the iterative process of editing and testing, and lets you color text to aid in reading the HTML code.
Adding forms to the "Create" field
The standard templates include a "Create" field that allows users to create new objects such as messages and documents. Users choose from a list of standard objects in this field. By default, the contents of this field reflect all forms that are available in this container.
You can add your new forms to this field, or replace the default contents of the field completely. The contents of the "Create" field are specified independently for messages and forms, with separate commands. This means that you can add or substitute message forms, for example, but leave the default document menu contents unchanged.
To add your forms to the "Create" field:
1 Add your forms to any lang.fc files.
2 Update the HeaderMatch document that is in the Internet Services folder.
To specify the message forms you want in the "Create" field, use the CUSTOMMESSAGES command, followed by the message form IDs, separated by semicolons. Message forms will appear in the dropdown menu in the order you list them here. Because this command overrides the default message forms in the field, only the message forms you specify will appear in the menu.
To specify the document forms you want in the "Create" field, use the CUSTOMFORMS command, followed by the document form IDs, separated by semicolons. Document forms will appear in the dropdown menu in the order you list them here, after any message forms. Because this command overrides the default document forms in the field, only the document forms you specify will appear in the menu.
TipTo check the form IDs of the default forms, open them in the FirstClass client, then choose Help > About this Window. The number to the left in the help window's title bar is the form ID (for example, the standard message form ID is 141).
If you don't specify one of these commands, the default contents will be used for that type of form.
NoteYou can use these commands to change the order in which forms appear in the menu. Remember that message forms will display before document forms.
For more information about the HeaderMatch document and VAR commands, including the order in which to add them when you are customizing multiple template sets, see the Internet Services help conference.
Example
The following example results in the "Create" field containing three of the standard message forms (141, 128, and 131) and a custom message form (1050), followed by two of the standard document forms (96 and 900) and a custom document form (2060):
*: VAR CUSTOMMESSAGES=141;128;131;1050
*: VAR CUSTOMFORMS=96;900;2060
| ||