How often do we use projects posted on "Share" ServiceNow community like Add to Update Set Utility?

[Joshua Prakash]

I  have created an app and wanted to share it with the community.

How often do we use projects posted on "Share" community
like "Add to Update Set Utility, Create Bulk UI Policy Actions for Catalog Items and Variable Sets etc.,"
Is it safe to use an app from "Share" community in Sub-prod instances?

[Mark Manders · Accepted solution]

What app did you create?
Share is a very good way to share your updatesets/apps, but with everything not officially supported by ServiceNow: you need to check what you are installing. First do it on your PDI to see if it does what you need. Then on your 'real' instance.

[Mark Roethof · Accepted solution]

Hi there,

Ah same question as you posted on LinkedIn 🙂

Once in a while I download something from Share, usually I try this on a PDI first and investigate whats in the update set etc.. If I don't understand the contents: no no to go to a customer instance.

Is it safe? In general I would say yes though in theory people can also Share crazy stuff, easter eggs, etcetera. Thats why: If I don't understand the contents: no no.

Also always ask yourself if there's not already something else available, out of the box, through a store application, etcetera. Some of the Share projects are really old, for example "Add to Update Set" / "Force to Update Set", there's almost the same out-of-the-box.

Personally I do regularly add Share projects, 30+ at the moment and still adding a few every year.

[Mark Manders · Accepted solution]

What app did you create?
Share is a very good way to share your updatesets/apps, but with everything not officially supported by ServiceNow: you need to check what you are installing. First do it on your PDI to see if it does what you need. Then on your 'real' instance.

[Joshua Prakash]

I have created an application for a third-party vendor in my PDI that integrates tickets from its customer's ServiceNow to its portal.

The vendor wants to buy an instance solely for creating tickets from its customer's ServiceNow to its portal.

What type of instance is needed?

What is the pricing of an instance that satisfies the above requirement?

What would be the cost of integration as it is bidirectional?

[Mark Manders · Accepted solution]

I think this vendor needs to get his requirements in order. Getting your own instance just so you can get tickets from a customer? That's an expensive thing. And you're not getting answers on cost on the community (and if you do, don't believe them). You will need to reach out to a ServiceNow rep to get this information, because they are the only ones that can tell you about the cost.
Have the vendor look at their current system and set up an integration between them. ServiceNow is too expensive to just use as ticketing tool. Or convince them to use it for more than just tickets.

[Mark Roethof · Accepted solution]

Hi there,

Ah same question as you posted on LinkedIn 🙂

Once in a while I download something from Share, usually I try this on a PDI first and investigate whats in the update set etc.. If I don't understand the contents: no no to go to a customer instance.

Is it safe? In general I would say yes though in theory people can also Share crazy stuff, easter eggs, etcetera. Thats why: If I don't understand the contents: no no.

Also always ask yourself if there's not already something else available, out of the box, through a store application, etcetera. Some of the Share projects are really old, for example "Add to Update Set" / "Force to Update Set", there's almost the same out-of-the-box.

Personally I do regularly add Share projects, 30+ at the moment and still adding a few every year.