What to do: |
|||||||||||||||||||||||||||||
![]() |
In this example you will learn how these dialogue forms have been created and how they are used to build this specific assistant. The general abbreviation for this assistant is , the main LogiView procedures are stored in the logic model .This assistant uses a set of three dialogue forms to prompt for specific data. With this information, the assistant creates:
All functions are performed in a database transaction. This ensures the consistency of the database. |
||||||||||||||||||||||||||||
![]() |
The first dialogue form of the given assistant is used to explain to the usage of the assistant and to prompt for the most significant data (user name and unique user identification code / UIC). The abbreviation for the first step of the assistant is (start). According to the naming conventions the name of the dialogue form is .Two sub-lists are used together with the dialogue form: The second sub-list is and it lists the user identification codes of all existing users. This list is another list on the same entity as used for the first sub-list.The set of buttons is automatically positioned in the lower right corner. Since there is no previous dialogue form, the button is deactivated, while it is possible to move to the following dialogue form or to abort the assistant.Open the first dialog formFrom the definition of the assistant, the LogiView procedure is executed to open this dialogue form. As you can see from the following listing, the explanation text is defined according to the current language (line 20 and 40). The userexit 'xform_call_dlg' is executed with several arguments (line 60):
Listing of LogiView procedure
Business Application Logic of the first Dialogue FormIn this rather simple dialogue form, the only business application logic are two post field userexits. These are implemented as LogiView procedures and check at once, if the entered user name and identification code are unique. |