Wiki source code of User Actions and user interface
Hide last authors
2.1 | 1 | = User interface and screen flow = | |
2 | |||
3 | The Requea platform provides user action flow to design, manage and extend user interfaces. Those user interface flows are called user actions or "actions" and are attached to entities. | ||
4 | |||
5 | User action define the flow of operation calls and screen that the user will see. | ||
6 | |||
7 | For example, the list user action is commonly defined with 2 steps: | ||
8 | |||
9 | |||
10 | * step 1: search the database, retrieve the records (entities) and return the result as a variable ("data") | ||
11 | * step 2: show the result (the "data" variable) as a list. The list may be a simple list, a multiple column table or a tree view for example.[[image:actions1.png]] | ||
12 | |||
13 | |||
14 | For more information about user actions, you can view the following articles: | ||
15 | |||
16 | * [[User action flow in detail>>ActionsFlowDetail]] | ||
17 | describes the different action blocks and the action sequence | ||
18 | |||
19 | * [[User interface personalization for forms and entity detail view>>UserInterfacePersoForm]] | ||
20 | how to change forms and entities detail view, add properties | ||
21 | |||
22 | * [[User interface personalisation for lists>>UserInterfacePersoList]] | ||
23 | how to change lists, add properties in multi-column tables |