Wiki source code of User Actions and user interface
Show last authors
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 | For more information about user actions, you can view the following articles: |
14 | |
15 | * [[User action flow in detail>>ActionsFlowDetail]] |
16 | describes the different action blocks and the action sequence |
17 | |
18 | * [[User interface personalization for forms and entity detail view>>UserInterfacePersoForm]] |
19 | how to change forms and entities detail view, add properties |
20 | |
21 | * [[User interface personalisation for lists>>UserInterfacePersoList]] |
22 | how to change lists, add properties in multi-column tables |
23 | |
24 | |
25 | = User action attributes = |
26 | |
27 | == instance action == |
28 | |
29 | An "Instance" action is an action that is available on one entity. (the instance). |
30 | |
31 | For example |
32 | * edit is an "instance" action: it work on one particular record |
33 | * list is not an "instance" action: it does not work on a particular record. It shows all the record |
34 | * new is not an "instance". It creates a new record, but does not start (work) on a particular record |
35 | * duplicate is an "instance" action. It copy an existing record (therefore, it works an a particular record). |
36 | |
37 | Instance actions should be checked as "Instance". |
38 | |
39 | Instance action: |
40 | - they are listed in a detail page, not listed on a list page |
41 | - the platform loads the instance and put it in the "data" variable. This is done automatically. |
42 | |
43 | == Visible Script == |
44 | |
45 | The visible script is used to hide / show actions for the user based on the context. The script is executed in the context of the instance object so the properties are accessed directly |
46 | |
47 | Examples of "visible script": |
48 | |
49 | {{code language="JavaScript"}} |
50 | |
51 | myProp == true |
52 | |
53 | myStatus == “Open” |
54 | |
55 | rqUser != null && rqUser.sysId == System.UserId |
56 | |
57 | System.User.hasAccess(“56647747477737733”); |
58 | |
59 | System.User.hasListAccess(data.sysWrite); |
60 | {{/code}} |
61 | |
62 |