Customizing Inputs for User Interaction Activities

Inputs for some user interaction activities can be customized. When workflows are executed in the CommCell or used in the Web Console as forms, the input screen can be customized to make it easier for users to enter data. For example, you can mark a field as required.

Procedure

  1. From the properties pane, click the Inputs tab and click Customize.

    The properties dialog box is displayed.

  2. From the left pane of the Inputs tab, select the input to customize.

    The right pane displays the options for the selected input.

  3. By default, the Type list shows the input type defined when the input was added. It can be changed by selecting a new value from the Type list.

  4. Enter a name in the Display Name box.

    This is the name users see when prompted to enter the input value during workflow execution. If a name is not entered, the input variable name is used.

  5. To prepopulate the input field during workflow execution, enter a value in the Default box.

    If a default value is not set, the input field is blank.

    Note:

    • The default value for boolean input types must be entered as either true or false.

    • If values are added to the Possible Values box, only those values may be used for the Default box.

  6. To define how the input field appears to a user during workflow execution, select a value from the Control Type list.

    The Control Type list changes depending on the input type:

    Type

    Control Type

    string

    TEXTBOX, MULTILINE, DROPDOWN, RADIOBUTTON, CHECKBOX

    integer, double, float, long, short

    TEXTBOX, DROPDOWN, RADIOBUTTON, CHECKBOX

    boolean

    CHECKBOX

    date

    CALENDAR, DROPDOWN, RADIOBUTTON, CHECKBOX

    dateTime

    DATETIME_PICKER, DROPDOWN, RADIOBUTTON, CHECKBOX

    time

    TIME_PICKER, DROPDOWN, RADIOBUTTON, CHECKBOX

    XML

    TEXTBOX, MULTILINE

    Binary

    FILE_PICKER, TEXTBOX

    For information on FILE_PICKER, see Customizing Inputs Using the FILE_PICKER Control Type.

    <Other>

    Changes depending on what is selected as the <Other> input type.

  7. Select Optional, Required, Read Only, or Hidden.

    • Required input fields are marked with an asterisk during workflow execution.

    • Mark an input field as Hidden when the input is passed in and users do not need to see it. For example, workflow inputs can be passed in when you use App Studio. For information about App Studio, see App Studio Overview.

  8. To define the data for control types, enter values in the Possible Values box:

    • DROPDOWN: The possible values are listed inside the drop-down box. Users are limited to these values during workflow execution.

    • RADIOBUTTON: The possible values are used as labels for the radio buttons.

    • CHECKBOX: The possible values are used as labels for the check boxes. During workflow execution, users can select multiple possible values if Create as list was selected when the input was first added. Users can select one of the possible values if Create as list was not selected.

  9. Click OK.

Loading...