Determining what your application needs to track
Gather the following information:
- What kinds of information do users need?
- What is the life cycle of the data? How long must data be stored? (Indefinitely, for N months or years)? What happens to data after this point?
- What types of information can be tracked together?
- Where does the data come from? Other systems? User input?
- Where could redundant data entry occur?
- Where can data be just referenced or displayed instead of entered or modified?
- Where can data be reused?
- Following normal business practices, when will the application's data become irrelevant?
The number of forms that you create depends on the smallest unit of data that you want to track and how you want that data to relate to other types of data. For example, to keep all data about assets in a single form, the asset form needs fields for information about manufacturers.
A complete trouble ticket application might consist of a main form that contains the caller ID, issue description, and work log information and several secondary forms that are linked to the main form to manage caller information or aging tickets. For complete descriptions of the key components that make up AR System applications, see the Key Concepts section.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*