- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I would to evaluate Workplace Service Delivery applications but cannot install them. Why are these applications blocked?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I checked this on my PDI, and I can see two different options when searching for “Workplace Service Delivery” in the Plugins module.
The first one is Workplace Service Delivery Suite (sn_wsd_suite), which is the full bundle that installs all Workplace Service Delivery applications together. This one includes dependencies like Microsoft Exchange Online Spoke, and that’s where the problem starts. On a PDI, the Exchange Online Spoke is marked as “installation blocked” because it’s a Store/IntegrationHub spoke dependency. Since the suite tries to install everything at once, and one of its required components is blocked, the entire suite installation gets blocked.
The second option is Core Business Suite for Workplace Services, which installs successfully on a PDI. It includes a few core Workplace apps, including sn_wsd_core. However, it does not contain all the applications that are part of the full Workplace Service Delivery Suite. So while you can test some core capabilities, you won’t get the complete WSD functionality from this package alone.
So the reason the Workplace Service Delivery Suite is blocked is not an issue with your instance specifically. It’s because PDIs do not allow installation of certain Store apps and IntegrationHub spokes that the full suite depends on.
If the goal is just evaluation, one workaround is to install the individual Workplace modules that are available on the PDI instead of installing the full suite. But if you need to test the complete Workplace Service Delivery Suite with all components, you would need a full sandbox or demo instance where those Store dependencies can be installed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @jna If you look at the screenshot, there are three plugins available. Clicking on any of them shows the Install button. If there is no Install button, a message will appear saying that the application cannot be installed on PDI.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I can see in my PDI after installation
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @jna
If you are getting this kind of dependency blocked error, it means those dependent plugin needs to intsall first in the instance
If that dependent plugin is from Servicenow store, In that case I guess Standard PDI instances generally do not support the installation of Store applications like this one directly from the instance's plugin list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I checked this on my PDI, and I can see two different options when searching for “Workplace Service Delivery” in the Plugins module.
The first one is Workplace Service Delivery Suite (sn_wsd_suite), which is the full bundle that installs all Workplace Service Delivery applications together. This one includes dependencies like Microsoft Exchange Online Spoke, and that’s where the problem starts. On a PDI, the Exchange Online Spoke is marked as “installation blocked” because it’s a Store/IntegrationHub spoke dependency. Since the suite tries to install everything at once, and one of its required components is blocked, the entire suite installation gets blocked.
The second option is Core Business Suite for Workplace Services, which installs successfully on a PDI. It includes a few core Workplace apps, including sn_wsd_core. However, it does not contain all the applications that are part of the full Workplace Service Delivery Suite. So while you can test some core capabilities, you won’t get the complete WSD functionality from this package alone.
So the reason the Workplace Service Delivery Suite is blocked is not an issue with your instance specifically. It’s because PDIs do not allow installation of certain Store apps and IntegrationHub spokes that the full suite depends on.
If the goal is just evaluation, one workaround is to install the individual Workplace modules that are available on the PDI instead of installing the full suite. But if you need to test the complete Workplace Service Delivery Suite with all components, you would need a full sandbox or demo instance where those Store dependencies can be installed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thanks for this information!
