Suppression of automatic interaction record

Question

Hi All,
I have a requirement like this:
User entered the business partner and confirm the account.
1) when user presses 'SAVE' button automatically interaction record will create(this is standard functionality working fine).
2) when user enters customer note or reason code and presses enter , BADI CRM_IC_IARECORD method BEFORE_IR_CREATE  should trigger, here i need to check customer entered note or not.
but at this point BADI is not triggering when user presses 'END' button.
How to activate this BADI everytime when user presses 'END' button.
Please give me advice , i am new CRM.
Thanks,
Rami.

Answer 1

Hello Rami
We did something similar whereby an IR would be created only if the reason field was populated and it works great. You need a good developer to help with this.
We created logic whereby the IR was created when a certain field was populated else nothing was created. In order to suppress the Interaction Record save, it was necessary to enhance the component with the u201CCancelu201D and u201CEnd Buttonsu201D:
Object(s) name     CRMCMP_IC_FRAME/HiddenView
The htmlb_event->server_event that is handled by the view controller for the hidden view (ZL_CRMCMP_I_HIDDENVIEW_IMPL is the view controller) is u201CforwardCallu201D. So the handler method is EH_ONFORWARDCALL. This method was redefined.
If either the u201CCancelu201D or u201CEndu201D button is clicked, the same htmlb_event is raised u2013 u201CforwardCallu201D, so the handler handles the same event for both buttons. It differentiates between the two buttons by the value that is held in attribute param1-value when the handler method is called. If the u201CCancelu201D button was clicked, then the value of this field would be 'CancelInteractionRequest', otherwise if the u201CEndu201D button was clicked it would be 'InteractionEndRequest'. These names correspond to the internal CRM event names.
In order to effectively suppress the interaction record from saving it is necessary to perform the same logic that would be called by the event handler if the u201CCancelu201D button was pressed. In other words, if the user clicked the u201CEndu201D button, in order to suppress the interaction record the system needs to first execute the cancel logic and then the end logic. However, we donu2019t want to suppress the automatic save of the Interaction Record if the Interaction Record has been filled in and can tell if the interaction Record needs to be saved by the value in the u201Creason codeu201D field on the interaction record. So, the double step of first calling the u201CCancelu201D logic and then the regular u201CEndu201D logic must only occur if the u201Creason codeu201D on the Interaction Record is blank. This can be done for any fields..
Regards
Muneeb