6.3 Creating forms

This section describes how to create new forms and add controls to it. It includes these sections:

6.3.1 Creating New Forms

  1. With provisioning request definition editor open, click the Forms tab.

  2. In the Form Selection section of the page, click Add to access the New Form wizard:

  3. Fill in the fields as follows:

    Field

    Description

    Form Name

    Type the name of the form as you want it to appear in Designer.

    Create a form using one of the templates

    If you want to base the new form on an existing template, select this option and select one of the forms from the Form templates list.

  4. Click OK to save the form or Cancel to exit without saving.

6.3.2 Working with Form Controls

Use the Form Controls section to define the content and layout of the form.

To add a control to a form:

  1. Click Add. Designer adds a control named Field to the bottom line of the form.

    If you add more than one control of the same name to the form, Designer adds a unique number to the end of the control name.

  2. Define the following properties for the control:

    Field

    Description

    Form Field Name

    A unique name for the field. The name is used in:

    • The Workflow tab’s Data Item Mapping dialog box.

    • The ECMA expression builder dialog box

    • An internal XML reference in the provisioning request definition file.

    Consider the naming conventions you want to use for form fields to avoid confusion in the Data Item Mapping and ECMA expression builder dialog boxes. For example, the request and approval forms might both contain a field called Reason. To make it clear which field you are working with while performing data mappings, you can preface the field name with the name of the form where it is used. You might name one reason field Req_Reason and the other App_Reason.

    Data Type

    The field’s data type. The data type determines the valid control types and the type of validation performed.

    Control Type

    The type of control used to display or edit the data. The selection list is filtered based on the selected data type.

    NOTE:Form field controls do not have Data Item Mappings or E-mail notifications property sheets.

  3. For each control, specify its properties in the Properties tab (available via Window > Show View > Properties). For more information, see Section 6.5, Form Control Reference.

  4. Click the Actions tab to define what the user can do with the form. For example, you can add actions that allow the user to submit a form or cancel it.

    NOTE:A request form must have, at a minimum, a SubmitAction. Without a SubmitAction, the request will not process. It is also recommended that every form also have a CancelAction. Each approval form must have at least one action defined.

  5. In the Actions page, click Add to add a new Action. Fill in the fields as follows:

    Field

    Description

    Actions Location

    Choose the location for the action buttons you add to the form.

    Bottom. Places the action buttons on the bottom of the form. (Default.)

    Top: Places the action buttons on the top of the form.

    Top and Bottom: Places the buttons at both the top and bottom of the form.

    Action Command

    Choose an action for the button. For more information, see Section 6.4, Action Reference.

    Data Type

    The data type associated with the action command. Valid choices are:

    Button—Adds a button to the form.

    Line Break—Allows you to define the layout of your action buttons. Adding a Line Break forces the buttons to the next line.

    Control Type

    The visual representation of the action command and data type. Button is the only valid entry.

Controlling Form Layout

The Designer places form controls on the form top to bottom and left to right. Use the Line Break control type to force the controls to the next line of the form.