is this a known bug in OMT vancouver? or it's my PDI

[Joshua Chen FX]

According to vancouver documentation, if you want to create a relationship between a CFS and RFS, you have to use ''composed of'' or ''bundles'' (because they are both type = Service Spec )

Source Specification	Target Specification	Relationship Type
Product	Service	Realized as
Product	Resource	Requires
Service	Resource	Requires
P/S/R	Same as the source specification	Bundles or Composed of

In my instance (vancouver), when I create from scratch 1 CFS and 1 RFS, I can use the ''composed of'' or ''bundle'' - sometimes i cant/sometimes i can. 

Once it's created, and I decide to delete the relationship - I cannot add a new ''composed of/bundle'' relationship because it forces me to use ''requires''. which is wrong or the intent is to use ''requires'' for CFS > RFS(?)

is this a known bug? or the documentation is wrong, and it's the correct behavior according to the BR that generated the errror message (screenshot below). 

see error message in screenshot below, trying to make a relationship between 2 Service Specs using ''composed of''

Additionally, the demo data for SD-WAN service package, has a ''composed of'' between CFS and RFS.
I deleted the relationship, and the system does not allow me to re-create it. it forces me to use ''requires''. seen screenshot below for comparison.

so is it CFS ''requiers ''RFS or  CFS ''composed of'' RFS in which case the system does not allow it.

[molayd · Accepted solution]

Hello Joshua,

This error is valid as Product Catalog framework treats CFSS & RFSS as separate business entities. The thumb rule I follow is "Use Requires whenever I see Resource, whether it Resource Facing Service Spec or Resource Spec".

Now as per TMF guidelines, below are the valid inter-domain relationships in NOW TSM PC, though the NOW framework doesn't stop you to make a relationship b/w PS & RFSS.

1. PS --> CFSS: Realized As
2. PS --> RS: Requires
3. CFSS --> RFSS: Requires
4. RFSS --> RS: Requires

Hope this helps.

Thanks.

[ShashankInamdar · Accepted solution]

Hi @Joshua Chen FX ,

You might want to refer to this article which explains the different relationship types and how to use them.

https://www.servicenow.com/community/telecom-articles/dyk-how-to-use-different-relationship-types-in...

Your observation with regards to the demo data is valid. In the very early versions of the Application, ComposedOf/Bundles was an allowed relationship between the CFSS-RFSS. Since then this has evolved but the demo data has not been repurposed for the new changes. Thank you pointing this out.

Regards

Shashank

[molayd · Accepted solution]

Hello Joshua,

This error is valid as Product Catalog framework treats CFSS & RFSS as separate business entities. The thumb rule I follow is "Use Requires whenever I see Resource, whether it Resource Facing Service Spec or Resource Spec".

Now as per TMF guidelines, below are the valid inter-domain relationships in NOW TSM PC, though the NOW framework doesn't stop you to make a relationship b/w PS & RFSS.

1. PS --> CFSS: Realized As
2. PS --> RS: Requires
3. CFSS --> RFSS: Requires
4. RFSS --> RS: Requires

Hope this helps.

Thanks.

[Michelle Murtha]

Yes, Requires is the correct relationship from CFSS to RFSS, and it's the only value you can save when creating the relationship.  But when you try to publish the CFSS with that relationship, ServiceNow gives the attached error

This is a brand new instance in Vancouver - provisioned less than 2 weeks ago.

[ShashankInamdar]

Can you please provide the OMT App version?

[Michelle Murtha]

Just installed last week: