HelpPages

Home | Developer | Frames | Screens | Transactions | Introduction to Transactions

Introduction to Transactions

    SCREENS - MOVEMENTS

    Traditionally, systems analysts have been talking for decades about master files and transaction files. Today, we talk about tables, but the concepts remain the same, although we talk about transaction tables, adopting the Anglo-Saxon style (transaction files). A transaction table is ultimately a table where operations are registered normally with a date and sometimes an hour applied to an element of a non-transactional table. An example may be a withdrawal funds from an ATM. In this case the non transactional element is the account number, while the transaction data includes the date, time, the amount withdrawn and the account number.
    This type of management of transactions is consider in our development system, under two points of view, different in appearance, but very similar in operation, tiny movements and fully movements. The difference is the number of screens needed to complete the operation. While the tiny movements, aimed at small-screen devices, typically used two or three screens, full motion, aimed at PCs are developed on a single screen with a central element of lines.
    So in a typical application of tiny movements, we have a first screen where you enter data common to the transaction, such as account number. We now turn to the "lines of movement", but each line is a full screen, moving to "next screen", "previous screen" to access the next or previous line (annotation). Finally we have a summary screen to complete all the transaction.
    This in a PC application, we would have a header, with information common to trasacción, a grid of lines for the movements, and optionally a foot or summary completion of the transaction.