IBM i General Design Standards › Design Standards for User Interfaces › Exploring and Backing Out

Exploring and Backing Out

The easiest way to learn how a system works is to take the options and see what happens: exploring is a far more natural learning mechanism than abstract conceptualizing, (for example, reading the instructions first). To allow the user to explore safely:

• Provide a ‘backing out’ capability to allow the user to retreat out of functions without affecting data.
• Stress the points of no return; for instance, by a confirm prompt or an exit menu.

In general, all update processing should take place immediately after the point of confirmation. There should not be intermediate displays from which the only exit route is one that requires further updating of the database, as this constitutes modal behavior. The commitment control facilities of OS/400 can be useful when designing to allow backing out, as multiple updates can be grouped to take place on an all or nothing basis. For example: