IBM Tivoli Web Access for Information Management

Chapter 9. Using shadow s-words and data attribute records 97

Figure 9-5 Fields in group REPORTER

Internally, Web Access requires that a data attribute record with the real s-word be used in the

data view record. The value entered by the user for the shadow data attribute record must

pass validation information for the data attribute record with the real s-word. This means that

if you add a new value to a shadow data attribute record, you must remember to add the value

to the data attribute record with the real s-word. Although it is acceptable to code a pattern

34

in the data attribute record with the real s-word that will cover all of the literal values in the

shadow data attribute record, you probably do not want to do that. This is because in inquiry

mode, the user could waste time trying to search with values that were never used in any

record, since a validation pattern such as CCV8 would allow the user to enter any nine

characters.

9.3 Building a shadow scenario

Before you try to implement shadowing in your application, you should have the basic group

and task layout completed. In our example above, you would use one data attribute record

(BLQ&PSAL) for each of the groups or tasks, or both, in which you want to include the Status

field. Once you have your basic layout completed, then you can start thinking about the fields

for which you would like to have different validation patterns in different places. Keep it

simple, and implement one field at a time.

Here are some basic steps:

1. Choose the field for which you want to set up shadowing.

2. Make a note of the name of the data attribute record for that field and the s-word that field

uses.

3. Determine how many shadows you need, that is, how many different groups of validation

patterns you need.

34

For example, CCV8.