You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/advanced/extensibility/user_exits.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# User Exits
2
2
3
-
abap2UI5 contains predefined user exits which can be used to modify the standard behaviour. The user exits are exposed by the interface [`Z2UI5_IF_EXIT`](https://github.com/abap2UI5/abap2UI5/blob/main/src/02/z2ui5_if_exit.intf.abap). To use them in your system you have to create a new class which implements the interface and its methods. They're called dynamically by abap2UI5 class [`Z2UI5_CL_EXIT`](https://github.com/abap2UI5/abap2UI5/blob/main/src/02/z2ui5_cl_exit.clas.abap). You should **not** include your class into abap2UI5 packages but in any other custom package.
3
+
abap2UI5 contains predefined user exits which can be used to modify the standard behavior. The user exits are exposed by the interface [`Z2UI5_IF_EXIT`](https://github.com/abap2UI5/abap2UI5/blob/main/src/02/z2ui5_if_exit.intf.abap). To use them in your system you have to create a new class which implements the interface and its methods. They're called dynamically by abap2UI5 class [`Z2UI5_CL_EXIT`](https://github.com/abap2UI5/abap2UI5/blob/main/src/02/z2ui5_cl_exit.clas.abap). You should **not** include your class into abap2UI5 packages but in any other custom package.
4
4
5
5
The following example changes the title, theme and the time drafts are saved in the backend:
Copy file name to clipboardExpand all lines: docs/configuration/authorization.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,6 @@ CLASS z2ui5_cl_app IMPLEMENTATION.
105
105
ENDCLASS.
106
106
```
107
107
108
-
::: tip Warning
108
+
::: warning
109
109
If you don't implement authorization checks at the app level, make sure that end users cannot bypass service-level authorization checks by navigating between apps.
Copy file name to clipboardExpand all lines: docs/configuration/btp.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
outline: [2, 4]
3
3
---
4
-
# BTP Build Workzone
4
+
# BTP Build Work Zone
5
5
6
6
Integrate your abap2UI5 apps into BTP Services like Build Workzone. Find all information here:<br>
7
7
[**Installation & Configuration of BTP**](https://www.linkedin.com/pulse/abap2ui5-integration-sap-business-technology-platform-13-installation-lf1re/?trackingId=YQ0y%2Fq0y6Kw5PK8chNCbrw%3D%3D&lipi=urn%3Ali%3Apage%3Ad_flagship3_pulse_read%3BFGBWUSIZRzeRjUNKBFD0uA%3D%3D)<br>
Copy file name to clipboardExpand all lines: docs/configuration/installation.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,10 +16,10 @@ In `S/4 Private Cloud` you can make the HTTP endpoint accessible for business us
16
16
### S/4 On-Premise
17
17
The setup in `S/4 On-Premise` is the same as in `S/4 Private Cloud`. Follow the guide [here.](/configuration/launchpad)
18
18
19
-
### R/3 Netweaver
19
+
### R/3 NetWeaver
20
20
The setup is the same as in `S/4 Private Cloud`. Depending on your release level, you may be able to add the apps to Launchpads. Follow the guide [here.](/configuration/launchpad)
21
21
22
-
### R/3 Netweaver (<7.50)
22
+
### R/3 NetWeaver (<7.50)
23
23
For older versions of R/3 NetWeaver lower v7.50, install the downported version with syntax adjustments for earlier releases. abap2UI5 runs on versions down to 7.02. See the downport section for more information [here.](/advanced/downporting)
Copy file name to clipboardExpand all lines: docs/configuration/s4_public_cloud.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ To use abap2UI5 in production environments, you'll need to complete the frontend
70
70
Since UI5 apps (BSPs) aren't supported directly via ADT abapGit, you need to manually deploy the app:
71
71
72
72
1. Download the app folder from [abap2UI5-frontend](https://github.com/abap2UI5/frontend)
73
-
2. Deploy it into your system following this [deployment guide](https://developers.sap.com/tutorials/abap-s4hanacloud-procurement-purchasereq-shop-ui..html#4c15de5c-bce6-46d0-a634-0008261b3117)
73
+
2. Deploy it into your system following this [deployment guide](https://developers.sap.com/tutorials/abap-s4hanacloud-procurement-purchasereq-shop-ui.html#4c15de5c-bce6-46d0-a634-0008261b3117)
Copy file name to clipboardExpand all lines: docs/configuration/security.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,8 @@ abap2UI5 is a backend-centric framework. All logic and business data remain secu
8
8
### HTTP Endpoint
9
9
The abap2UI5 framework operates as an HTTP handler. You create this HTTP handler and call the abap2UI5 API within it. End users can access abap2UI5 by calling the endpoint externally, with security managed similarly to any other UI5 application.
10
10
11
-
### Authentication
12
-
Authorization is handled at the ICF (Internet Communication Framework) node level. You have complete control over configuring the ICF node, including visibility settings, login procedures, and other security parameters.
11
+
### Authentication
12
+
Authentication is handled at the ICF (Internet Communication Framework) node level. You have complete control over configuring the ICF node, including visibility settings, login procedures, and other security parameters.
13
13
14
14
### Authorization
15
15
As an app developer, you have full flexibility in managing authorization settings. You can configure these either at the application level or service node level. For detailed guidance on setting up authentication for your endpoint, check out [this page.](/configuration/authorization)
0 commit comments