RTO & RPO tracking in CMDB

[Krunal2]

Hi,

We recently noticed that ServiceNow has provided RTO & RPO Fields under Mirror Template (cmdb_ci_mirror_template) class. We would like to understand

1) Why ServiceNow has only created fields under this class ?

2) Is there any way, we can move these fields to CMDB_CI or Business Application level ?

Thanks,

Krunal Thanki 

[Harish Bainsla]

1. Why Fields in cmdb_ci_mirror_template Class:

   • ServiceNow periodically introduces new features and updates, including enhancements to its data model. The addition of specific fields to a particular class might be related to the use case or functionality associated with that class.
   • The cmdb_ci_mirror_template class may be specifically designed to store configuration data related to mirroring or replication, and hence, fields like RTO and RPO might be relevant in that context.

2. Moving Fields to Other Classes:

   • Modifying the base data model, such as moving fields between classes, is generally not recommended and can have significant implications on the platform's stability and future upgrades.
   • ServiceNow provides extensive customization options through the use of tables, fields, and relationships. If you have specific requirements for RTO and RPO at the CI or Business Application level, it's recommended to explore customization options within the existing data model.
   • Consider creating a new table or extending an existing table (if possible) to accommodate these fields at the desired level. Then, establish relationships between these tables and the relevant classes.

It's essential to follow best practices for customization, including thorough testing in non-production instances before implementing changes in a production environment. Additionally, you may want to check the official ServiceNow documentation and community forums for any updates or discussions related to the specific fields and classes you are working with.

As the ServiceNow platform evolves, there may be changes, improvements, or additional features introduced, so staying informed about the latest releases and documentation is valuable for ServiceNow administrators and developers. If possible, consult with your organization's ServiceNow administrator or ServiceNow support for guidance tailored to your specific instance and requirements.

[Krunal2]

Thank you Harish for detailed response. 

Generally RTO & RPO are majorly being tracked at business application or process / service offering level. It would be helpful, if I can get more idea around which use case ServiceNow is trying to target by adding these fields only into cmdb_ci_mirror_template class. 

With regards to moving fields, my question was specifically to move fields from child class to parent class. Is it possible ? Specifically, if I want to move these fields from cmdb_ci_mirror_template table to cmdb_ci talbe, so these fields are easily available to any class. 

I am completely in agreement with you explanation of not creating overhead of customization. 

Regards,

Krunal Thanki

[VaranAwesomenow]

I agree with your comments that RPO and RTO are attributes of a business application and hence it make sense to see those fields in cmdb_ci_business_app

[Sean Lucas]

I agree with the challenges listed here. Business Continuity Management module also needs to add in functionality where business process and/or BIAs can drive this at the business application level.