Data Manager Policy question

Lucky1
Tera Guru

3 weeks ago

Hello all,

 

In the CMDB Workspace, when we click on the Data Manager, then we get an option to create a new policy, 
So, today evening, I have created a new Retire policy. 

So, during creation of new Retire Policy, selection of oob Subflow (Retire Configuration Items) is mandatory, and I have selected it.

and then I have Published the policy. No error. Even Retirement Definitions are ok.

 

But my question is, when I checked the scheduled jobs, (cmdb_policy_scheduled_job), then it is showing nothing on that policy name.
So, how the CMDBTASK records gets created for this Retire Policy????

 

Is it like, do I need to wait for one day, to check the scheduled jobs or how it works?

 

 

My good, if someone explains me better.

 

Thanks you.

 

 

 

Regards,

Lucky

0 Helpfuls
  • 737 Views
5 REPLIES 5

Lucky1
Tera Guru
In response to Sarthak Kashyap

3 weeks ago - last edited 3 weeks ago

Hello Sarthak,

 

Thanks for your response.

Yes, I have gone through those links initially.

Apart from that, I found a scheduled job, CMDB Data Manager Retire Policy Processor

that runs and creates, the CMDB Tasks, 

Also, as I said earlier, while creating the policy, there is a sub-flow added:

Lucky1_0-1765187073259.png

 

And here is the Sub-flow looks like

Lucky1_1-1765187165798.png

 

 

 

The CMDBTASK when created, it is triggering Approval to me, and Once I approve that task, then all the CIs that satisfies the policy, are getting retired.

 

Now, what I am don't able to understand is,

From where that approval is being triggered? There is no approval part, in the sub-flow also.

Can someone help me here?

 

 

 

Regards,

Lucky

 

 

 

 

 

 

 

Regards,

Lucky

 

0 Helpfuls

Laveena-Agarwal
Kilo Sage
In response to Lucky1

3 weeks ago

Hi @Lucky1 ,

 

I spent some time digging into this to understand where exactly the “Approvals” are coming from. Here are the findings:

  • The logic is handled through the Script Include "CMDBDataManagerTaskApprovalHelper"

  • This Script Include triggers the approval process via a subflow

  • The subflow being used is "CMDB Task approval subflow"

As a general best practice, we should avoid modifying any OOB components, as once we customize them, we fully own the maintenance.

 

My recommendation would be: if customization is absolutely required, create our your copy of both the Script Include and the Flow. This will ensure you don’t lose out on any future enhancements or upgrades to this functionality.

 

I hope this helps. Please give it a thumbs up and mark it as the accepted solution so others can benefit too.

Tony Branton
ServiceNow Employee
ServiceNow Employee

3 weeks ago

Data Manager includes a number of OOB scheduled jobs that run on a daily basis.  The CMDB Data Manager Retire Policy Processor scheduled job processes Retire policies and creates Data Manager tasks. You can change the schedule for the scheduled job such as changing the time it starts, however you should avoid setting the frequency to intervals shorter than a day especially when dealing with a large CMDBs.  Using too short a frequency with large CMDBs could see a scheduled job never finishing before the next one is scheduled to begin with the result that no tasks are generated.

 

The OOB sub-flow for Retire (and Archive & Delete) policies is used to control the task approval flow - the sub-flow is not used to generate tasks.  Note that you can copy the OOB sub-flows to suit your own approval processes (e.g. you may want multiple approval steps) which is why the sub-flow is selectable.

 

Hope this helps.

0 Helpfuls