Why did our "Custom Application" become a "Store Application" after promotion via the app pipeline?

[Rob44]

We've got a custom app built out in DEV. I went ahead and configured the app pipeline (no Git) and promoted form DEV to TEST via a Deployment Request. The app was promoted to TEST however in TEST the scope is defined in the "Store Application" table instead of the "Custom Application" table.

We've updated a couple other custom features to look at the parent "Application" table but we're seeing some other issues with it being a "Store Application" as well for example the "Background Scripts" tool doesn't list the scope at all with it being a "Store Application" where "Custom Applications" do show in the scope drop down.

Ideally we would like to promote via the App Repository (without Git) while maintaining the app's status as a "Custom Application" vs a "Store Application" is that possible?

[Swathi P]

Hi ,

The Application Repository is part of the ServiceNow Store. The application repository allows ServiceNow customers to upload and distribute applications between their instances. When you access the application repository, you can see and manage only the applications that are published by your own organization. So, whatever applications are published via application repository to other instances can be seen as Store Application rather than Custom Application since application repository is part of ServiceNow Store.

 In case , if you want to run any Background scripts please use Fix Scripts rather than back ground script. Fix Scripts act as background scripts.

Don't give a constant values in scripts as they will be non editable in test instance if we push via application repository  so use application properties instead.

If you want to have Custom Application in test instance you can move the application via updatesets.