Business Application and Application Services - status mapping and field synchronization

[elbab]

Hi All!

Are you using any validation rules or status mappings to make sure Business Applications have at lease one Operational Application Service? Are you synchronizing any fields between the records in general?

Thank you!

[Mathew Hillyard]

Hi @elbab,

This is a gap in the platform currently. You are able to retire a Business Application when it has related Application Services whose Operational status is not retired. A relatively simple before update Business Rule should be able to check for operational linked App Services and and abort the update with a suitable error message if any are found. Generally the Business Application should be the last object in a CSDM service that you retire, so I would not advise cascading the retirement from Business Application to Application Service.

It's worth mentioning that the key field in Business Application (if not using Life Cycles) is Install status, but for Application Service it is Operational status - so your Business Rule will need to take account of this.

In terms of data cascade, I don't see a lot of usable data in Business App that would suit being copied to Application Service - plus you would probably need to set the fields on App Service to read only then establish a process for mastering and updating the data. The point of CSDM is its relationships, so you can easily see that an App Service is an instantiation of a Business App, and where possible I try to locate data in one place then use database views for reporting requirements if needed rather than cascade fields across records - except where they're essential, such as support or ownership.

I hope this helps!

[debendudas]

Hi @elbab ,

In ServiceNow, ensuring that Business Applications have at least one Operational Application Service can be achieved through various methods, including Business rules. Here are some strategies you can consider:

• You can create a Business Rule that runs on insert or update of a Business Application record. This rule can check if there is at least one related Application Service with an Operational status. If not, it can prevent the save operation and prompt the user to add an Operational Application Service.
• Another option is to use a Client Script to perform a similar check on the client side before the form is submitted.
• Set up a Scheduled Job to periodically check for Business Applications without an Operational Application Service and take necessary actions, such as sending notifications to the responsible parties or automatically updating records.

When implementing these strategies, it's important to consider the specific requirements of your organization and the impact on existing processes.

If this solution helps you then, mark it as accepted solution ‌‌✔️ and give thumbs up 👍! 

[Mathew Hillyard]

@debendudas 

A scheduled job is not necessary - CMDB Query Builder can do this, and if you are using the Enterprise Architecture application there is a pre-configured Query in the baseline.