Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about how to analyze the memory cleaning strategy of SAP CRM WebClient UI. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

If we search for 5 PPR and go to the account, and then go to PPR again, the search results still exist.

Why do these two kinds of navigation lead to different behaviors?

We must remember some key points:

WD_DESTROY is called every time you leave the current view, either the child view's own redefined implementation or the parent view's default implementation.

DESTROY method of context node class will be called one by one.

In PPR case, since RESULT node in view controller is mapped to RESULT in component controller via context binding, so collection wrapper will not be cleared.

Instead it will just clear the context node reference itself.

Let's record down the real BOL collection in collection wrapper before CLEAR me- > typed_context.

{ORV 1253 *\ CLASS=CL_CRM_BOL_ENTITY_COL}

After clear is executed, we check {Orange 1253 *\ CLASS=CL_CRM_BOL_ENTITY_COL} in debugger:

The 5 PPR BOL entities are still there:

This means that WD_DESTORY will clear only the context node reference itself, not the real BOL content in the BOL wrapper.

The BOL content is cleared only if:

When navigation is performed, a frame event is raised:

CL_CRM_UI_SESSION_RESTART works as event handler and will clear bol buffer by evaluating flag gv_bol_reset_requested.

In lv_bolcore_reset the 5 PPR entities will be deleted in BOL container.

So now question is when is gv_bol_reset_requested set?

For example if you click "Home"

Framework will evaluate if the navigation target is a Workcenter.

If so, the framework event before_context_change will be raised.

The event handler for it will simply set restart_requested flag to'Xuan.

Later this flag will be evaluated and set gv_bol_reset_requested.

If you click only the work center view, such as "Accounts", line 91 will not be executed, so the requested gv_bol_reset_ will always be equal to abap_false.

After reading the above, do you have any further understanding of how to analyze the memory cleaning strategy of SAP CRM WebClient UI? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.