You do not own the vendor prefix for this scope

[Anirban Roy]

Hi,

We are working on a known integration - Servicenow to Terraform integration.

We have imported the 3rd party application named 'Terraform' via source control as it is not available in servicenow store 

We understand that the app can be moved via update set, however Is it possible to deploy the app to further instances using publish and install option? 

While trying to publish the app, we are getting the below error because the app is built by 3rd part and thus company scope prefix wont match with the external app provider's scope.

**********************************************************************************

To summarize, I am trying to follow the below method to import the 3rd party scoped app, do some development and then move the application across instances along with my custom changes without xml import/ update set movement -

 

Looking for the best practices in this scenario. All suggestions are welcome.

Regards,

Anirban

[Pradeep Sharma · Accepted solution]

Hi Anirban,

This is the expected behavior. You cannot use an external party application and publish it to your company instances via Publish to the App Repo option. The only possible solution here is to recreate the application from scratch in the right scope if the intention is to build an application.

- Pradeep Sharma

[Anirban Roy]

Thanks @Pradeep Sharma for a quick response.

I was really looking for a confirmation to not miss out any opportunity otherwise. 

Additionally, can you help me understand how store apps developed by partners are allowed to be published and installed in company instances (the partners vendor prefix would vary from consumer company's prefix). I read that the store app creators need to register with TPP program and are assigned vendor instances. Does this mean that vendor instances would hold 'snc' prefix and the 'snc' prefix mismatch will be ignored while publishing the app in app repo.

PS: For our use case, we are planning to do an initial package import via source control integration and then move the remaining via update set movement.

[Pradeep Sharma]

Each company will have a scope key assigned from ServiceNow. All the apps developed internally can be shared to target instances that belong to the same company. That said, if the intention is to publish an app to the store then you have to develop those apps on vendor instances  (**assigned to registered TPP partners**)

That said, I don't think there will be an issue if you move the files via update set for an application that is build on some other company instances. Please be aware you will also be prevented from publishing this app to the store as the vendor key is not assigned to your company.

I hope that helps.

- Pradeep Sharma

[Anirban Roy]

Hi Pradeep,

Thanks again.

I was just curious to know how 3rd party store apps are not shown the same error message while publishing on company instances. I know that in the 'HI' portal, the requestor has to select the entitlements to make the app available on different company instances but I was trying to understand if the scope prefix of the 3rd party store app would be 'snc' or still the developer specific scope e.g. 'x_32789'.  

PS: I have marked your first response as the correct answer as it was related to my original post. However, I will be glad if I could get a response on this related question.

Looping @Brad Tilton , as I saw some helpful articles on this topic.

Regards,

Anirban