update

Author: oblomov-dev

docs/development/logging.md

@@ -3,11 +3,11 @@ outline: [2, 6]
 ---
 # Logging, BAL
 
-Logging is essential for developing end-user business processes. In ABAP systems, the standard tool for this is the Business Application Log, which is supported in both on-premise systems and ABAP Cloud (via new APIs). With abap2UI5 you can use the BAL functions as you would do it in classic development. to display logs just create a table with the entries or use predefinded popups of the framework.
+Logging is essential for developing end-user business processes. In ABAP systems, the standard tool for this purpose is the Business Application Log (BAL), supported in both on-premise systems and ABAP Cloud (via new APIs). With abap2UI5, you can use BAL functions just as you would in classic development and create a table with the entries or use predefined popups provided by the framework.
 
-###### BAL structure
-In on-premise ABAP systems, you can use the classic BAL APIs. As no specific logging object exists, simply import the BAL table into `z2ui5add_cl_bal_cl`:
-```abp
+##### BAL Variables
+In ABAP classic, you can use the classic BAL function modules and display the BAL table with the popup `z2ui5_cl_pop_messages`:
+```abap
 METHOD z2ui5_if_app~main.
 
   DATA(lt_bal) = VALUE bal_t_msgr(
@@ -18,73 +18,66 @@ METHOD z2ui5_if_app~main.
 
 ```
 
-###### ABAP Cloud Log
-Similar to messages you can display bal log directly in the message_popup. Just drop the into it:
+##### ABAP Cloud
+In ABAP cloud, you can just import the logging object into the message popup:
 ```abap
 METHOD z2ui5_if_app~main.
 
-    DATA(lo_log) = cl_bali_log=>create( ).
-    DATA(lo_msg) = cl_bali_message_setter=>create(
-        severity   = if_bali_constants=>c_severity_status
-        id         = 'DEMO_LOG'
-        number     = '002'
-        variable_1 = `username` ).
-    lo_log->add_item( lo_msg ).
+  DATA(lo_log) = cl_bali_log=>create( ).
+  DATA(lo_msg) = cl_bali_message_setter=>create(
+    severity   = if_bali_constants=>c_severity_status
+    id         = 'DEMO_LOG'
+    number     = '002'
+    variable_1 = `username` ).
+  lo_log->add_item( lo_msg ).
 
-    DATA(lo_bapi) = cl_bali_message_setter=>create_from_bapiret2( 
-        VALUE #( type       = 'E'
-                 id         = 'DEMO_LOG'
-                 number     = '002'
-                 message_v1 = 'Dummy' ) ).
+  DATA(lo_bapi) = cl_bali_message_setter=>create_from_bapiret2( 
+    VALUE #( 
+      type       = 'E'
+      id         = 'DEMO_LOG'
+      number     = '002'
+      message_v1 = 'Dummy' ) ).
+  lo_log->add_item( lo_bapi ).
 
-    lo_log->add_item( lo_bapi ).
-    client->nav_app_call( z2ui5add_cl_bal_cl=>factory_popup( lo_log ) ).
+  client->nav_app_call( z2ui5_cl_pop_messages=>factory( lo_log ) ).
 
 ENDMETHOD.
 ```
 
-
-###### abap-logger
-
-you can also use the abap logger in the it is built in an running
-In on-premise systems, you also have the option to install the open-source project [**abap-logger**](https://github.com/ABAP-Logger/ABAP-Logger), which simplifies logging with BAL. Here’s an example of how to use it with abap2UI5:
+##### abap-logger
+In on-premise systems, you also have the option to use the fantastic open-source project [**abap-logger**](https://github.com/ABAP-Logger/ABAP-Logger). This tool simplifies working with BAL logs and integrates seamlessly with abap2UI5. Here’s an example:
 ```abap
-CLASS z2ui5add_cl_abap_logger_sample DEFINITION PUBLIC FINAL
-  CREATE PUBLIC .
-
-  PUBLIC SECTION.
-    INTERFACES z2ui5_if_app.
-
-ENDCLASS.
-
-CLASS z2ui5add_cl_abap_logger_sample IMPLEMENTATION.
-
-  METHOD z2ui5_if_app~main.
-
-    DATA: log TYPE REF TO zif_logger.
-    log = zcl_logger_factory=>create_log( object = 'ZINTERFACES'
-                                          subobject = 'ACCOUNTING'
-                                          desc = 'Stuff imported from legacy systems' ).
+METHOD z2ui5_if_app~main.
 
-    log->e( 'You see, what had happened was...' ).
-    client->nav_app_call( z2ui5add_cl_abap_logger_ui=>display_popup( log ) ).
+  DATA(lo_log) = zcl_logger_factory=>create_log( 
+            object    = 'ZINTERFACES'
+            subobject = 'ACCOUNTING'
+            desc      = 'my abap-logger logger' ).
+  log->e( 'There is an error...' ).
 
-  ENDMETHOD.
+  client->nav_app_call( z2ui5_cl_pop_messages=>factory( lo_log ) ).
 
-ENDCLASS.
+ENDMETHOD.
 ```
 
+##### BAL Popup
+Compared to T100 messages, BAL logs include more detailed information, such as timestamps. You can also use the BAL log popup to display this information. All the examples above can be used as is, but for the popup app, you should use the `z2ui5_cl_pop_bal` popup instead:
 
-#### BAL Popup
-Comparet to T100 the BAL log contains a lot more specific information. You can also use the ballog popup to get more detailed information.
-
-
-In ABAP Cloud environments, the BAL includes a new API. Use this API to import logging objects directly into the class `z2ui5add_cl_bal_cl` to display messages:
+```abap
+METHOD z2ui5_if_app~main.
 
+  DATA(lo_log) = zcl_logger_factory=>create_log( 
+            object    = 'ZINTERFACES'
+            subobject = 'ACCOUNTING'
+            desc      = 'my abap-logger logger' ).
+  log->e( 'There is an error...' ).
 
+  client->nav_app_call( z2ui5_cl_pop_bal=>factory( lo_log ) ).
 
+ENDMETHOD.
+```
 
 ::: tip
-This popup is in its early stages, with basic functionality currently available. If you’ve implemented BAL functionality with abap2UI5, consider sharing your work! Contributions and pull requests are welcome. 
+This popup is still in its early stages, offering basic functionality. If you’ve implemented BAL features with abap2UI5, consider sharing your work! Contributions and pull requests are always welcome.
 :::