Skip to content

Commit e5bc1b2

Browse files
authored
Update rap.md
1 parent 9d271e8 commit e5bc1b2

File tree

1 file changed

+6
-13
lines changed
  • docs/technical/technology

1 file changed

+6
-13
lines changed

docs/technical/technology/rap.md

Lines changed: 6 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,11 @@ This page provides a technical comparison between **RAP** and **abap2UI5**, focu
1717
| **UI Definition** | Annotations in CDS & metadata | XML Views created directly in ABAP |
1818
| **Communication** | OData V4 (metadata, data, actions) | Simple HTTP requests (Over-the-Wire) |
1919
| **Runtime Control**| Logic partly changeable via RAP Implementation | Full control over UI and logic in backend |
20-
| **Model** | Defined at designtime via CDS | Designed at Designtime or Runtime via Internal Tables |
20+
| **Model** | Defined at designtime via CDS | Designed at Designtime or Runtime via Internal Tables |
21+
| **Drafts** | Managed via RAP drafts on Model Level | Managed via Serialization on App level |
2122

22-
### 2. State Management
2323

24-
| Aspect | RAP (Fiori Elements) | abap2UI5 |
25-
|----------------------------|-------------------------------------------------------|-----------------------------------------------------|
26-
| **State Definition** | Managed via RAP drafts and transaction control | Centralized in ABAP ViewModels |
27-
| **Frontend Involvement** | UI5 components manage transient state | Frontend has no independent state management |
28-
| **Persistence** | Via RAP persistence layer | Reflected through ViewModel updates |
29-
| **User Interaction Flow** | Triggers OData actions, state managed across layers | Triggers backend events, state is updated in ABAP |
30-
31-
### 3. Developer Workflow
24+
### 2. Developer Workflow
3225

3326
| Aspect | RAP (Fiori Elements) | abap2UI5 |
3427
|----------------------------|------------------------------------------------------|--------------------------------------------------------|
@@ -40,7 +33,7 @@ This page provides a technical comparison between **RAP** and **abap2UI5**, focu
4033
| **Complexity** | High: multiple layers & technologies | Low: one language, one layer |
4134

4235

43-
### 4. Client–Server Communication Flow
36+
### 3. Client–Server Communication Flow
4437

4538
#### RAP
4639

@@ -63,7 +56,7 @@ Backend (ABAP Class)
6356
└──> Processes event, updates ViewModel, returns changes
6457
```
6558

66-
### 5. Flexibility & Runtime Capabilities
59+
### 4. Flexibility & Runtime Capabilities
6760

6861
| Aspect | RAP (Fiori Elements) | abap2UI5 |
6962
|---------------------------|---------------------------------------------|------------------------------------------|
@@ -73,7 +66,7 @@ Backend (ABAP Class)
7366
| **Learning Curve** | Steep (new concepts, multiple layers) | Flat (ABAP-only, no metadata tooling) |
7467

7568

76-
### 6. Cloud Readiness & Compliance
69+
### 5. Cloud Readiness & Compliance
7770

7871
| Feature | RAP | abap2UI5 |
7972
|----------------------------|-----------------------------|-------------------------------|

0 commit comments

Comments
 (0)