|GUIStyle Product Implementation: Required Screens|
|Product:||Strategi - GUIStyle|
In order to implement the GUIStyle Product for your application, you may have been asked to
record a set of screens from your application. These screens will then be played back at
ADVANCED BusinessLink, where GUIStyle will be implemented against them. It is important that
the screens recorded be representative of the bulk of your application, so that patterns designed
based on those screens are more likely to work on screens you have not recorded. This document
gives you guidelines on which to base your choice of which screens to record. For instructions
on how to record screens, reference Strategi Screen Recording.
It is assumed that your application employs some degree of standardization for how screens have been implemented. If you have multiple standards through your application, it is important to represent these in your samplings. For example, if Function Keys are sometimes denoted as "F5=Refresh" and sometimes as "CK5 Refresh", you should record at least one screen employing each standard.
Below is a list of the most important GUIStyle components which can be recognized through patterns. In addition to describing these components, for each component we give a recommended minimum number of screens which you should record that show that components. If you do not record at least that many screens containing that component, we are unlikely to be able to give you a robust implementation of the pattern for that component.
Obviously, most screens will contain several components. For instance, recording three subfiles that include subfile options, titles and function keys will satisfy the minimums for both subfile and subfile options, and leave you with only two more screens to record showing titles and function keys.
By providing an adequately balanced and representative set of recorded screens, you will ensure that the resulting GUIStyle implementation more fully GUI-izes your application.
** End of Technical Support Bulletin **