- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
We are using the Foundation data sync plugin to sync CMDB records to our customer. It looks like this plugin might be non-functional as of the current 2.3.26 release. In previous releases this worked without issue.
After a consumer submits a request for an FDS offering, the subscription is not shown on the request record so it cannot move forward. See attached screenshot.
I have replicated the issue on a pair of PDI's as well. In previous releases this worked without issue. The definition is confirmed to have the "auto acknowledge FDS requests" value set to true.
@Kenny Caldwell Is this a known issue in this release?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I did a little research and it looks like this may be an issue with Security Center version. The specific role this message references is sn_vsc.security_center_admin. This role comes with Security Center 3.2.5. My instance is on 3.4.2. Check your Security Center version and update. Hopefully this works!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago - last edited a month ago
When you upgraded FDS, did you also upgrade Service Exchange to the same version?
Just tested and it does auto upgrade Service Exchange. So not the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Yes, Service Exchange for Providers, Foundation Data Sync for Providers and Foundation Data Sync are all on Version: 2.3.26
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Try creating an offering without Auto Acknowledge. See what happens.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Record shows up in the receive state with no subscription. Clicking acknowledge updates the state but has no effect on the subscription related list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @Kenny Caldwell really appreciate your help on this!
I have done some deeper tracing and found something that stands out. It still remains that once I upgrade to 2.3.14 or newer the issue starts in both my PDI and copy of production instance.
What should happen when a consumer requests and FDS definition
- "insert Consumer Inbound Offering Request" goes from consumer to provider (no sub record expected yet)
- The following comes back from provider to consumer
---"update Foundation Data Provider Request"/sn_fds_con_offering_request
---"insert Foundation Data Provider Subscription"/sn_fds_con_subscription (this is not coming back or getting sent by the provider)
What do the logs say?
com.snc.process_flow.exception.ProcessAutomationException: Attempted to add black listed role: [c562ee15ff3a2210c212ffffffffff25]:
com.glide.schedule_v2.SchedulerWorkerThread
It is the same sys_id on both my PDI and copy of production instance. SN KB has an article on the generic error. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1642669
