Practices for App Engine Studio

shansingh75
Giga Contributor

What are the best practices while working on App Engine Studio?

4 REPLIES 4

folusho
Tera Guru

@shansingh75 

 

I modified this reply based on comments from Paige and also from my expereicce using App Engine. Hopefully it can help you:

 

 

  • Start with a clear data model – Define tables, fields, and relationships early using the Data tab.

  • Use scoped applications – Avoid using the Global scope to prevent unintended system-wide changes.

  • Leverage Flow Designer – Use flows and subflows for automation instead of scripts when possible.

  • Apply proper security – Configure ACLs and test access with non-admin users.

  • Follow naming conventions – Use consistent, descriptive names for tables, fields, and flows.

  • Use Record Producers for intake – Make data entry user-friendly and script-free.

  • Test with impersonation – Validate behavior and permissions from different user roles.

  • Document everything – Add descriptions to flows, tables, and fields to aid future maintenance.

  • Promote changes through proper channels – Use Update Sets or Application Repository for deployment.

  • Collaborate via Delegated Development – Assign appropriate roles to team members for safe collaboration.

 

Paige Duffey
ServiceNow Employee
ServiceNow Employee

 

Hello! I believe this response was generated by AI, but unfortunately it’s not accurate or particularly helpful.

 

For instance, what is meant by “App Documentation”? In AES, there isn’t a built-in feature to “generate technical specs.” The “App Summarization” feature can give a brief overview of an app, but it’s not the same as technical documentation—and it also requires additional licensing.

 

Similarly, the term “Preview As” isn’t quite correct here. There is a way to impersonate users if you have the right roles. You can also preview some record types during development to see what something will look like. However, this is not a substitute for thoroughly testing by impersonating users with different roles.

 

In short: AI tools are great for quick answers, but it’s crucial to check their responses for accuracy—sometimes they can include “hallucinations” or made-up content. Please double-check before sending AI-generated information.

@Paige Duffey 

Thanks for your response and corrections are noted.

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @shansingh75 

 

Using AES means you want to create a custom app, so there aren’t any special best practices specific to AES.

 

https://www.servicenow.com/community/developer-forum/best-practices-for-managing-and-deploying-custo...

 

https://www.servicenow.com/community/developer-forum/what-is-the-best-practice-for-customizing-appli...

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

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