As you begin to create a custom form, you need to decide how many and what types of custom fields that you need. You should make some notes and have a rough idea of how you want each field to look.
@task lets you create six types of parameters that are outlined in Table 10.1. When creating a parameter, you need to name a parameter, provide a description, choose the type of parameter from the Display Type menu, set the display size, and select the data type. Figure 10.2 shows the screen you use to enter this information.
Table 10.1 lists the parameter display types and explains the characteristics of each parameter type.
N O T E : Depending on the size of your screen resolution settings, browser type, and other variables, one display size value may display differently between users. A display size that looks correct to one user may cascade over the edge of a screen for another user. You should test your parameters and adjust your display sizes as necessary before fully distributing them.
For some of the parameter display types, you must set the parameter options. Parameter options let you create labels for radio buttons, check boxes, and menus. They also set the field values for the tables in the database. Further, you can use them to hide selected values or set default selections for values. Figure 10.3 shows an example of the Parameter Options screen.
N O T E : Values for the database must be unique.
The following is an illustration of how and when a user might need to create a parameter.
Lisa owns an independent medical lab and her clients include many hospitals and clinics. Often hospitals send her patient samples and request a standard set of tests. Lisa uses @task to track her work and assign tests to her technicians. She has created several projects and tasks for each set of tests, however, Lisa needs some custom data to attach to her projects. She needs to capture information about which client a request came from and what set of tests was requested.
Lisa begins by creating two parameters, one to track clients and one to track requests. For the parameter to track clients, Lisa creates a new parameter, names it, and describes it. Because she has many clients and each request comes from a single client, she selects a drop-down menu as the display type. Hospital names can be long, so she selects a display size 0f 200, and a data type of text.
In the Parameter options screen, she types the name of every hospital she has as a client, and uses the Move arrows to organize them with her best clients at the top of the menu. Figure 10.4 displays Lisa's parameter options.
She also creates a parameter for the set of requested tests. She uses a multi-select drop-down menu for this parameter because some clients request multiple sets of tests, and she fills in the other fields as she did for the first parameter. In the Label fields of the parameter options screen, she types the names of all the test sets that she can do.
Lisa also wants to keep track of whether her clients are up to date on their payments, so she creates two parameters to keep track of their status and how much is owed. She creates radio buttons to show the status, and a text field for a balance amount.
One of the test sets Lisa does is related to impaired drivers. When she receives a request for one of these tests, she creates a project for it. In this project she has a task to test for blood alcohol, and a different task to test for each kind of illegal drug that can impair judgment and ability. However, for her tasks, she needs custom data to record whether test results are positive or negative. She creates a parameter for this using two radio buttons. For this parameter, most of the time results are negative, so she selects negative as the default parameter.
Now that Lisa has created all of her parameters, she wants to group them in her forms using parameter groups.