Legacy - Development considerations
-
- UpdatedAug 1, 2024
- 1 minute read
- Xanadu
- Building applications
When you are developing code, consider some of these suggestions for the most efficient performance.
Important: You've landed at the legacy version of Studio, which will be supported until the Australia release in Q1 2026. Try building and editing apps in the new version of ServiceNow Studio instead. For more information, see Building applications with ServiceNow Studio.
- Production instances shouldn’t publish to the Git repository
- To protect the integrity of production, you shouldn’t push changes to publish to the Git repository from production even though technically you can open and commit changes in the application in ServiceNow® Studio. The “Can Edit Application in Studio” option can be disabled in production on the sys_app record. But it resets at the next source code operation that triggers an update (that is, when you apply remote changes or switch branches).
- Dependencies are not installed when installing an application from the Git repository
- Source-controlled applications do not automatically install or upgrade if they are listed as the dependency of your application. Instead, the customer must install or upgrade the source-controlled application on its own. The customer is also responsible for installing and upgrading the applications in the correct order.
- Tight control on source control privileges in production
- The source code operations are generally available to those with development privileges in the instance. Since production environments shouldn’t have ongoing development, be sure to tightly control admin and delegated development privileges to avoid data loss and other serious consequences.