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

[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

[Michelle Murtha]

This explains why the current version and the demo data don't work together, but it doesn't explain what is happening in Vancouver now.
In both my PDI and my client's brand new instance (glide-vancouver-07-06-2023__patch5-12-01-2023), I can save the Specification relationship between CFSS to RFSS as Requires.  Any other choice gives me an error.  But when I go to Publish the CFSS, I get this error:

Has anyone found a workaround for this?  Can we disable this relationship checking or fix the underlaying data table that it is checking?  Has SN come out with a patch for this yet?

[Joshua Chen FX]

@Michelle Murtha  @ShashankInamdar 

you can deactivate  >>> Business Rule (BR) named "Validate Chars and Related Specs OOTB" which is triggered when the status changes to "publish''

and it will allow you, but i would wait for SN to reply, because i dont know what else this would impact

[Mahesh_Krishnan]

@ShashankInamdar 's article was very helpful in understanding the relationship types and how they influence order decomposition.

[Michelle Murtha]

I have the same problem in both my PDI and my client instance.  I originally selected Requires for a CFSS to a RFSS relationship.  When I went to publish, it says I have to use Composed of or Bundles.  So I go to change the relationship and it says you have to use Requires.

I can only save the relationship as a "Requires" but then the CFSS cannot be published.

Something is NOT right here...