Include standard save functionalities in Z view

Question

Hi,
we've created a new component (view) which is shown when displaying an IBASE (component IBMAIN). On top of the IBASE maintenance screen in the web UI you can find buttons for editing data, cancel editing or save changes.
The save button is displayed as soon as you click the editing button, however, it is inactive. As soon as you change any data, the save button becomes clickable.
Saving data seems to be triggered by event EH_ONSAVE in class CL_IBMAIN_IBMAINVIEWSET_IMPL.
The thing is that we'd like to extend our view that the standard functions are supported, means, as soon as we change anything in our view, the save button should be active (by triggering a data changed event), when clicking the save button, our data should be saved as well.
We found class CL_CRM_BOL_TX_MANAGER which seems to hold data and flags for information having been changed.
Is there any quick guide on how to use this default feature?
Many thanks & regards
Wolfgang

Answer 1

Hi Wolfgang,
A code similar to this, in the method where you are adding the buttons will make the Save and Edit Button in Sync.
Save:
Data: lr_entity  TYPE REF TO cl_crm_bol_entity,
* Get the current entity which is currently being edited
  lr_entity ?= me->typed_context->context node name->collection_wrapper->get_current( ).
  CHECK lr_entity IS BOUND.
* Button SAVE
  CLEAR ls_button.
  ls_button-page_id  = me->component_id.
  ls_button-on_click = 'save'.
  ls_button-type     = cl_thtmlb_util=>gc_icon_save.
  ls_button-enabled = lr_entity->is_locked( ).
  APPEND ls_button TO rt_buttons.
Edit:
data: lv_enabled    TYPE crmt_boolean,
  lv_enabled = me->view_group_context->is_view_in_display_mode( me ).   
  ls_button-type     = cl_thtmlb_util=>gc_icon_edit.
  ls_button-on_click = 'EDIT'.
  ls_button-text = cl_wd_utilities=>get_otr_text_by_alias( 'CRM_UIU_BT/EDIT' )."#EC NOTEXT
  ls_button-enabled  = lv_enabled.
  APPEND ls_button TO gt_button.
  CLEAR ls_button.
Class CL_CRM_BOL_TX_MANAGER should be fine for saving, before that you can use either of methods  CHECK_SAVE_POSSIBLE,  CHECK_SAVE_NEEDED.
Please do a where used for sample code or look into event handlers of any of standard components like SEGED_TG/EFTARGETGROUP.
Regards,
Masood Imrani S.