Scope requirement for applications to be published in the ServiceNow store

KrithikaV
Tera Expert

Hi,

 

We developed an application in the Personal Developer Instance (PDI) which we downloaded to our vendor instance through source control. When I try to publish the app to our Application Repository, I get the error: You do not own the vendor prefix for this store.

I looked into the forum and found this article that gives some tips on fixing this issue. 

 

We are gearing up to publish the application to the ServiceNow Store. After publishing the application to the  Application repository after changing to the vendor scope, do we again have to do this kind of scope change when we have to publish to the ServiceNow store?

Tagging @Pradeep Sharma 

 

Thanks in advance,
Krithika

 

 

1 ACCEPTED SOLUTION

Marco0o1
Tera Sage

Hi @KrithikaV , 

 

Basically Yes, is not possible to publish an Application from the PDI, and basically the steps to "Migrate" to other scope are the followin:

1- Create new Scope on the correct instance with the prefix (Can be done on the Studio module)

2- Now that all data diferent from tasks/cmdb/assets are stored in the sys_metada table

3- The scrip just go to each reacord in the previous scope and make a copy in the new scope

 

You are not migrating exactly, you are creating a copy into the new scope from the previous custom scope to a new one, that include forms/widgets/portals/most of everything. Maybe you will need to take a look in some parts like custom roles and some stuff that can be hardcoded by sys_ids because those are diferents and need to be mapped to the new one.

 

var gr = new GlideRecord('sys_metadata');   
gr.addQuery('sys_scope','821b35cd4f442200bbc32d118110c7f2'); //sys_id of the first scoped app

gr.query();

while(gr.next())


{

gr.sys_scope = '96784d274f10e600bbc32d118110c7de'; //Update with correct scope i.e newly created scoped app   

gr.setWorkflow(false);   

gr.update();   

}

 

 

View solution in original post

1 REPLY 1

Marco0o1
Tera Sage

Hi @KrithikaV , 

 

Basically Yes, is not possible to publish an Application from the PDI, and basically the steps to "Migrate" to other scope are the followin:

1- Create new Scope on the correct instance with the prefix (Can be done on the Studio module)

2- Now that all data diferent from tasks/cmdb/assets are stored in the sys_metada table

3- The scrip just go to each reacord in the previous scope and make a copy in the new scope

 

You are not migrating exactly, you are creating a copy into the new scope from the previous custom scope to a new one, that include forms/widgets/portals/most of everything. Maybe you will need to take a look in some parts like custom roles and some stuff that can be hardcoded by sys_ids because those are diferents and need to be mapped to the new one.

 

var gr = new GlideRecord('sys_metadata');   
gr.addQuery('sys_scope','821b35cd4f442200bbc32d118110c7f2'); //sys_id of the first scoped app

gr.query();

while(gr.next())


{

gr.sys_scope = '96784d274f10e600bbc32d118110c7de'; //Update with correct scope i.e newly created scoped app   

gr.setWorkflow(false);   

gr.update();   

}