Define Information Lifecycle Management
For product standard requirements, it is necessary to provide our customer the choice to delete the facebook posts and tweets stored in CRM database table according to their dedicated consent requirement. In this blog I will show you how to implement the destruction object for social post destruction. You can follow it to create your own destruction object.
ILM Retention Management is a licensed product, which is really due to the fact that the predecessor to full ILM capability was data archiving which was always included as part of the core suite.
Double click the created entry, maintain the component for it. In my case I use "Customer Relationship Management" for it.
Also specify the data destruction execution report name.
Create a new entry for your destruction object:
Double click "Allowed Start Time", specify which field is considered by ILM framework to judge whether a post could be destructed.
Here I choose the IRM constant CREATION_DATE. It is just a constant but NOT the field of your database table. Later on we will map this constant to the real field of the database table.
In "Allowed Policy Category", choose RTP as policy category.
Double click on Object Category-Specific customizing, specify your BOR object name below:
Mapping the IRM constant CREATION_DATE to the field of your database table:
In my database table I have CREATION_DATE_TIME to store the timestap of post creation, and UUID for post unique identifier.
Specify the key field name of your database table.
Till now we have finished all the customizing. The new step is to implement destruction report CRM_SOCIAL_ILM_DES.
The selection screen of report could be found below. It allows you to specify whether the destruction report is only written into application log, or also output to list besides application log, or only list. The Run comment can enable you to maintain an explanation text of each run so that you can easily find the run information later in application log according to the comment.
Most of the jobs have been done via the utility class cl_crm_soc_destruct_ilm_tool. The source code could be find from attachment.REPORT CRM_SOCIAL_ILM_DES.
CALL METHOD cl_crm_soc_destruct_ilm_tool=>run
iv_comment = p_coment
iv_test_mode = p_test
iv_detail_log_option = space
iv_output_option = p_prot_o.
The key point is in method PROCESS_POST_WITH_FOLLOWUP. In this method as developer you do not need to check whether a post could be destructed. Instead, you tell the ILM framework which field of database tabe is used as destruction evaluation and ILM framework will tell you the result whether a post is destructible.DATA: lv_field_value TYPE if_lrm_bs_types=>ty_s_tabname_fieldname_values,
lx_rule_exec TYPE REF TO cx_lrm_rule_exec,
lv_destructible TYPE lrm_destructible,
dref_uuid TYPE REF TO crmd_soc_post-uuid,
You might also like
三维设计拐点来临-记2014Bentley电力行业研 — 赛迪网
Bentley 应势推出了自己的资产信息全生命周期管理（Asset Lifecycle Information Management，ALIM）解决方案。不但如此，Bentley 还在近年推出了“中国唯一”和“中国优先”策略，专门成立了一个多达30人的团队，专门针对 ..