Want to understand other enterprise customer use of SWP and Jobs & Tasks around the following scenario:
Publishing almost all applications in SWP based on varying level of access to the application to allow level II support team members the ability to install any application as needed, allowing the end user access to approved applications and request applications vs. leveraging jobs & tasks > packages delivery tasks to deploy based on a service request recevied.
I understand the main concept for SWP (used it over many years) is to allow users to request software applications whether approved or request approval and to reduce support calls, etc. I get the overall theme. However, what's the point of leveraging a delivery task when you can toss everything and everyone into a single solution, IE. SWP and have at it there.
Questions I have:
- How do you leverage SWP today?
- Do you leverage Job's and Tasks and SWP equally? If so, why this way vs. the option below?
- Do you leverage SWP for both end users and client support teams and not leverage Jobs and Tasks? If so, why not leverage the above option?
- Challenges you have experienced with SWP? Preferrably on the 7.5 platform but if 7.1, please specify
- Are there limitations / impact to the SMP and or end user SWP agent experience based on so many applications (hundreds of apps) published?
- What, if any, would be any other concerns and or recommendations if this is the route we went to basically steer away from Jobs and Tasks for software.
A bit of background, I have mainly leveraged Jobs and Tasks (package delivery task) and SWP mutually over 6.9 and 7.1 platforms - depends on what is needed out in the SWP.
No where in any best practices or user guides does the scenario above present itself in such a way as to leverage the SWP as the prominent single location to install applications. Note: I'm merely asking the questions to understand how others are leveraging SWP and why.
I'm interested in hearing how others leverage both of these solutions and are they leaning toward one or the other for day to day tasks or looking at liberating the end user, growing the self service model even further by steering away from package delivery tasks and allowing both the end user and the support teams a single location to request and install applications.
Let me hear your thoughts / concerns / recommendations.