Skip to content

Commit 9d1ee3d

Browse files
authored
Update dx.md
1 parent a8b81fc commit 9d1ee3d

File tree

1 file changed

+22
-3
lines changed
  • docs/advanced/technical

1 file changed

+22
-3
lines changed

docs/advanced/technical/dx.md

Lines changed: 22 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
# DX: ALV & Selection-Screen Style?
22

3-
4-
hello world small app
5-
3+
### As simple as possible
64

75
```abap
86
CLASS zcl_app_adt DEFINITION PUBLIC CREATE PUBLIC.
@@ -36,6 +34,8 @@ CLASS zcl_app_ui5 IMPLEMENTATION.
3634
ENDCLASS.
3735
```
3836

37+
### Tables
38+
3939
```abap
4040
REPORT zre_app_alv.
4141
@@ -53,6 +53,25 @@ cl_salv_table=>factory(
5353
go_salv->display( ).
5454
```
5555

56+
57+
### Inputs
58+
```abap
59+
REPORT zre_app_input.
60+
61+
PARAMETERS pa_arbgb TYPE t100-arbgb DEFAULT 'MDG_TR'.
62+
63+
START-OF-SELECTION.
64+
MESSAGE |Input: { pa_arbgb }| type 'I'.
65+
```
66+
67+
68+
69+
### Events
70+
71+
72+
73+
74+
5675
##### 9. One HTTP-Service for all Apps
5776

5877
First, we do not define a specific HTTP-Service for transmitting the View and the Data. Instead, every app uses the same generic HTTP-Handler including two strings (one for the View and one for the Data) eliminating the need to develop individual OData-Services with SEGW or CDS. During runtime the ABAP variables & tables are transformed into a JSON-Model and transmitted as a string to the frontend. In JavaScript it is parsed again into a JSON-Model and binded to the UI5-View:

0 commit comments

Comments
 (0)