Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

CFS requires RFS error

Joshua Chen MTL
Mega Sage

Hello,


I was able to create a CFS requires RFS relationship, but the second one i tried - i got this error:

I tried to do the following:

  • Mobile SMS Service (CFS) requires RFS = (RFS).

Got the error message below telling me to use relation type  ''budnle/composed'' 

  • my RFS is of type : resource facing
  • my CFS is of type : service facing
  • what am i doing wrong? i noticed i get this error when
    • I try to publish a CFS while my RFS is not published
      • I get error message that my target spec is not published
    • I go to my RFS (target spec) to publish
    • Now, cant publish my CFS because ''requires'' does not work'' anymore after i geet my first error msg
    • I deactivated BR ''validate relation type'' and stil lget error

JoshuaChenFX_0-1706282397389.png

 

 

RFS

JoshuaChenFX_2-1706282426998.png


ALSO script productutil.. says prevent us to make ''require'' when its sys_class = service specification??
then this script is wrong? 

JoshuaChenFX_0-1706284533374.png

 

 

.
Add me on LinkedIn 🙂 https://www.linkedin.com/in/joshuachen0510/
2 ACCEPTED SOLUTIONS

@Joshua Chen MTL @Michelle Murtha I can now confirm these issues were fixed in the latest OMT App. I shall encourage you to upgrade to the latest OMT App available on store.

View solution in original post

@Joshua Chen MTL - build the 'requires' relationship between the CFS and RFS - but ensure both the specs are in published state. I expect you not to face the issue. While this is not the final solution, until the fix is delivered I expect this to work. 

Please let me know if this works for you.

View solution in original post

12 REPLIES 12

ShashankInamdar
ServiceNow Employee
ServiceNow Employee

Hi @Joshua Chen MTL ,

We have seen this reported in the recent past. I will get this checked if this was a bug that got fixed.

It will be useful if you can provide the Platform version and OMT App version you are using.

 

I tried reproducing the issue with the exact same steps, but did face the error.

I am on Vancouver platform with OMT v5.2.0

 

Also FYI, the Script Include part you have posted has the following intention -

Return an error (the one you are getting) suggesting to use Composed Of/bundles when the Spec Type between the Source and Target Specs is the same AND where currently the Spec Relationship type = Requires.

 

Thanks

THANK YOU!  

 

@ShashankInamdar 

Vancouver, 5.00


.
Add me on LinkedIn 🙂 https://www.linkedin.com/in/joshuachen0510/

@Joshua Chen MTL @Michelle Murtha I can now confirm these issues were fixed in the latest OMT App. I shall encourage you to upgrade to the latest OMT App available on store.