- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2024 07:22 AM - edited 01-26-2024 07:56 AM
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
- I try to publish a CFS while my RFS is not published
RFS
ALSO script productutil.. says prevent us to make ''require'' when its sys_class = service specification??
then this script is wrong?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2024 01:09 AM
@Joshua Chen FX @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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2024 10:06 AM
@Joshua Chen FX - 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2024 01:07 PM
can you clarify which version for which app?
I've found 3 different apps:
- sn_om_tmt: latest version is 6.0.2
- sn_csm_order_mgmt: latest version is 5.0.0
- sn_ind_tmt_orm: latest version is 6.0.3
My client's instance (still having the issue) has the following installed:
- 6.0.3 sn_ind_tmt_orm
My PDI instance (still having the issue) has the following installed:
- 6.0.2 sn_om_tmt
- 6.0.3 sn_ind_tmt_orm
It appears that I have the latest versions installed in two different instances, and both are still having the issue. These are the same versions we installed in the past two weeks, so I'm not sure what the "latest" version that has the fix is...
Should we open HI tickets at this point?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2024 01:54 PM
@Michelle Murtha As you may know, ServiceNow has had two separate Order Management Applications - CSM OM and OMT.
In the November release, the two Order Management products were converged to have a common code base to enable scale and faster pace of innovation.
Going forward, you should not be using sn_csm_order_mgmt (v5.0.0).
Also, this App should not be installed on the same instance as the OMT one. I expect this App to be retired from the store from the Washington release onwards.
The converged OM app is sn_ind_tmt_orm (v6.0.3)
For additional industry specific capabilities and access to Open APIs, Telecom and Tech companies are encouraged to also have the add on sn_om_tmt (v6.0.2)
You do seem to have the latest plugins. If this is still an issue, please do raise a ticket.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2024 08:51 AM
@ShashankInamdar @Michelle Murtha
we are having the issue again, it does not allow us to do ''CFS requires RFS''
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2024 10:06 AM
@Joshua Chen FX - 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2024 08:56 AM
I ended up not raising a HI ticket, only because we decided to only use Product Specs for our first implementation, not Service Specs... @Joshua Chen FX I would open a ticket so they can look into the specifics of your instance. Good Luck!