Step 2: Test Features of the Prototype

Defining Dialogs Using ADSC › Instructions For Executing the Application › Step 2: Test Features of the Prototype

Step 2: Test Features of the Prototype

The first function executed in the sample application is DEPTMENU. According to your application design, the following responses are valid from DEPTMENU:

ADD selects dialog function ADDDEP. In the final application, ADDDEP will allow users to add new department information in the database.
MOD selects dialog function MODDEP, which will allow users to modify existing department information in the database.
DEL selects dialog function DELDEP, which will allow users to delete department information.
EXIT selects system function QUIT, which will allow users to leave the application.

Test out each of the above responses while you are executing the Department application prototype. For example, try specifying the ADD response:

Specifying the ADD Response

To specify the ADD response, you can use any of the following methods:

Press [PF4] to select the ADD response
Type a nonblank character in front of a response and press [Enter] to select the response.
Type the response name (ADD) after the RESPONSE: prompt, and press [Enter].

DIALOG: PAGE: 1 OF: 1 DATE: 08/19/99 NEXT PAGE: DEPARTMENT INFORMATION APPLICATION MAIN MENU x ADD (PF4) ADD A NEW DEPARTMENT _ MOD (PF5) MODIFY A DEPARTMENT _ DEL (PF6) DELETE A DEPARTMENT _ EXIT (PF9) TERMINATE APPLICATION RESPONSE: add SEND DATA-─► MODE: STEP

ADDDEP Function

The ADDDEP function is displayed with the XXXMAP.

FUNCTION: ADDDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: NAME .....: HEAD ID ..: NEXT RESPONSE:

The ADDDEP function allows the user to enter information about a department. Try tabbing between variable fields and entering sample department information. You cannot type anything in the FUNCTION: field because you made it a protected field.

FUNCTION: ADDDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: 9012 NAME .....: Application Testing HEAD ID ..: 3456 NEXT RESPONSE:

ADDDEP is a skeleton dialog, which means that you haven't added any process logic to the dialog. The dialog cannot access the database. Therefore, your sample data is not stored when you press [Enter].

Input-Handling Operations

Other input-handling operations are performed automatically at runtime. For example, your sample input is:

Echoed on the screen after you press [Enter].
Tested for invalid values and redisplayed in bold when errors are found.
For example, try entering invalid values in the DEPARTMENT ID and HEAD ID variable fields:

FUNCTION: ADDDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: xyz NAME .....: Quality Assurance HEAD ID ..: xyz RESPONSE:

In this case, the runtime system returns an error message:

**ERROR AT 7,24** **ERROR AT 9,24**

Nonnumeric data is invalid for the DEPARTMENT ID and HEAD ID variable fields because you enabled the CA ADS automatic editing feature for these numeric fields in in Chapter 8.

For more information on how automatic editing can be used to keep users from entering invalid values, see the CA IDMS Mapping Facility Guide.

You also can test the NEXT RESPONSE variable field. You can try entering undefined responses (for example, UPDATE) or responses that are valid for the application but not for the ADDDEP function (for example, MOD). In fact, a user testing the Department application prototype probably would try to access the MODDEP function from ADDDEP to see if newly added department information can be modified easily if, for example, the department name is misspelled.

Enter new department values on the screen, and then specify the MOD response to try accessing MODDEP from ADDDEP:

Specifying the MOD Response from ADDDEP

FUNCTION: ADDDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: 4567 NAME .....: System Software Division HEAD ID ..: 9521 NEXT RESPONSE: mod FUNCTION: ADDDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: 4567 NAME .....: SYSTEM SOFTWARE DIVISION HEAD ID ..: 9521 RESPONSE: DC172008 *** UNACCEPTABLE RESPONSE. PLEASE TRY AGAIN ***

Even though MOD is defined for the application, it is not valid from the ADDDEP function. According to your application definition, only the following responses are valid from ADDDEP:

BACK selects system function POP, which returns execution to the previous menu function (in this case, DEPTMENU).
EXIT selects system function QUIT, which terminates the application.

Display the MODDEP Function

To display the MODDEP function from ADDDEP, you must first access a function from which MODDEP is valid. Since MOD is valid for the DEPTMENU function, use the BACK response to return to DEPTMENU, and then invoke MOD from DEPTMENU:

FUNCTION: ADDDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: 4567 NAME .....: SYSTEM SOFTWARE DIVISION HEAD ID ..: 9521 RESPONSE: back

Choose MOD from the DEPTMENU screen to display the MODDEP function.

DIALOG: PAGE: 1 OF: 1 DATE: 08/19/99 NEXT PAGE: DEPARTMENT INFORMATION APPLICATION MAIN MENU _ ADD (PF4) ADD A NEW DEPARTMENT x MOD (PF5) MODIFY A DEPARTMENT _ DEL (PF6) DELETE A DEPARTMENT _ EXIT (PF9) TERMINATE APPLICATION

The MODDEP function is displayed

FUNCTION: MODDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: NAME .....: HEAD ID ..:

Display the DELDEP Function

To display function DELDEP, you first return to the DEPTMENU function. From DEPTMENU, you can invoke DELDEP as shown:

FUNCTION: MODDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: 0000 NAME .....: HEAD ID ..: 0000 RESPONSE: back

Select the DEL response to display DELDEP

DIALOG: PAGE: 1 OF: 1 DATE: 08/19/99 NEXT PAGE: DEPARTMENT INFORMATION APPLICATION MAIN MENU _ ADD (PF4) ADD A NEW DEPARTMENT _ MOD (PF5) MODIFY A DEPARTMENT x DEL (PF6) DELETE A DEPARTMENT _ EXIT (PF9) TERMINATE APPLICATION

The DELDEP function is displayed.

FUNCTION: DELDEP DEPARTMENT INFORMATION DEPARTMENT ID .......: 0000 NAME .....: HEAD ID ..: 0000 RESPONSE:

Continue to test the application prototype until you are familiar with the Department application prototype. When you are finished testing the application, exit from the application as described below.