App development on my PDI

[VL10]

I thought my PDI would be ready to go to develop a simple app and publish and test.

but I get this error:
App Engine Studio needs more setup. Ask your admin to check the pipeline configurations for this instance. You can try to submit again, later.

So, I checked and got this support article:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0960297

However that takes me to this screen:

 

 

which then takes me to this screen:

Can someone tell me how  to format/enter the values here:

Instance URL: I add the base URL

Instance Credential: not sure what to use

So I am stuck.

[AnveshKumar M]

Hi @VL10 ,

You have to create credential in connection and credential alias to fille the credential field  here.

[VL10]

Thanks, is there any default setup that we can get for some simple beginner app dev work, or some documentation you can point me at?

[Arun_S1 · Accepted solution]

Hello @VL10,

Not sure what is your understanding towards the environment and the requirement to create a new environment record.

Generally when you develop an application the environments are used to specify the instances that are used for Development, Testing & Deployment. In the screenshot you are connecting to the same environment where you are already working in fact you should connect to a different instance and the user name & password to the connect to that instance should be created as an credential aliases.

More over if you wanted to develop a simple application and test in the same instance you need not create environements.

Please see the below link for more  information about envrionments.

https://docs.servicenow.com/bundle/rome-application-development/page/build/app-engine-studio/task/cr... 

Please mark the appropriate response as correct answer and helpful, This may help other community users to follow correct solution.

Thanks!!

[tahaappdevelop]

Thank you for your input, but I respectfully disagree with some aspects of your suggestion. As an app developer, it's crucial to set up a proper environment configuration to ensure the scalability and proper testing of the application. While I understand that you may not always need multiple environments for simple apps, it’s important to distinguish between local testing and preparing an app for future deployment.

In ServiceNow, environments help simulate real-world deployment scenarios, especially when we need to differentiate between development, testing, and production stages. Even if I’m working on the same instance, setting up an environment properly helps prevent configuration issues and ensures I don't accidentally affect the core instance while developing. This becomes especially critical when moving beyond basic apps, where version control and environment-specific configurations come into play.

Furthermore, you mention that I should connect to a different instance and create credential aliases. While this is certainly a valid approach for more complex workflows, it’s essential to recognize that App Engine Studio allows for configuring environments and credentials in a way that enhances the overall workflow—especially for an app developer who is working on a project that may expand. These configurations ensure that the right permissions and connections are in place as the application moves through the development pipeline, making it more robust and scalable in the long term.

It’s also important to note that using the Instance URL and Instance Credentials in the configuration doesn't just serve as a method of establishing a connection; it also plays a vital role in managing secure access across different environments. Without this setup, an app could face security risks or fail to scale properly in a larger enterprise environment.

I believe that creating environments isn’t just about working on a simple application in isolation; it’s about setting a proper foundation that anticipates future stages of the app’s lifecycle. Even if this is a simple app, I want to ensure I'm following best practices so that as the app evolves, it won't encounter roadblocks when scaling or moving to different instances for testing or deployment.

Again, I appreciate your suggestion, but as an app developer, I’d prefer to follow a more structured approach to ensure future-proofing my application for real-world use cases.