Parent/child in Business Applications

gwolfkill
Tera Contributor

This may be a naive question, but I'm looking for the specific way to create the parent/child scenario on the Business Application table. Say we have an overarching software suite with the different "modules" inside of it. My understanding is that we would list the overall suite as well as the modules individually on the Business Application table. How do you specifically create that "relationship"? Do you use the 'Platform Host' attribute on the modules to reference the overall suite, or something else? Is this simply an attribute reference or a true relationship on the relationship table? If the latter, which one?

4 REPLIES 4

Barry Kant
ServiceNow Employee
ServiceNow Employee

can be done like the attached example

To add to this, the system will force you to select a Platform host if you select the architecture type Platform App.

find_real_file.png

 

This could be an attempt from the side of ServiceNow to force a Platform App to have a single host. You could then add a flow/business rule that creates/updates/deletes the Depends on::Used by relation between the app and the host whenever the Platform host field is updated.

Alternatively you could include 'related items' in the dependency view to get it to show up.

In terms of, what you mentioned regarding a software suite, I am not sure this fits within the realm of Platform App and Host. As you can see from Barry's example the idea is that the Host is something ServiceNow and the Apps are configuration thereof, e.g. Incident or Change.

Depending on whether I am reading your question correctly, I am getting more of a Microsoft Office or Adobe Creative suite vibe, which to me is an entirely different beast than the Platform App/Host.

I'm not sure there actually is a proper recommendation for this, but I would be more inclined towards utilizing the software model/software package table for this information.

 

Best regards,

Casper

Mark Bodman
ServiceNow Employee
ServiceNow Employee

I don't recommend an "endless" parent / child hierarchy for Business Apps as this is a portfolio.  Structure should adhered to, as the CSDM example Barry posted for Platforms.

More detail about this approach can be found here: https://community.servicenow.com/community?id=community_question&sys_id=8eb947e5db5cdbc01dcaf3231f96...

 

Damy
Kilo Contributor

This was a helpful post. We are in the process of defining our Business App portfolio as well and we structured it per CSDM by using setting Architecture Type = Platform Host (Parent) and Architecture Type = Platform Application (Child aka "modules"). For relationship type, we used Depends On::Used By.