What are examples of changes to an instance that should NOT be part of an Application?

Changes to an instance that should not be part of an Application typically include modifications that are not directly related to the application’s purpose or functionality. In this case, the correct answer encompasses all the given examples.

For instance, configuration on forms or lists for tables that are not part of the application implies that these adjustments are made to tables that the application does not utilize. This could lead to unnecessary complexity and management overhead, as the modifications may not be relevant or needed by the application itself.

Scripts associated with tables that are outside the application also fall into this category. Like form configurations, these scripts may complicate the maintenance of the application and could introduce potential issues or performance impact without contributing to the intended functionality of the application.

Moreover, changing system property values is another significant example of an alteration that should be regarded separately from the application changes. System properties often apply globally across the ServiceNow instance and can affect how various applications behave or interact. Modifying these properties can have implications far beyond a single application, which is why they are typically best left out of application-specific code.

Thus, each of these examples emphasizes the principle that changes which are not inherent to the structure and requirements of the application itself should be managed distinctly, reinforcing the value of maintaining a clear