Is a global object application an appropriate place to store non-application-specific, reusable objects?

A global object application is indeed an appropriate place to store non-application-specific, reusable objects. This is because global object applications serve as a centralized repository for objects that can be utilized across multiple applications within the Appian environment.

The primary purpose of a global object application is to promote reusability and maintainability by allowing developers to create, manage, and access shared components, functions, rules, constants, and other entities without duplication. By placing non-application-specific objects in a global object application, teams can ensure that their investments in building these components can be leveraged as needed across various projects, thus fostering standardization and reducing redundancy.

In contrast, choices that suggest documentation or temporary usage do not capture the full intention of the global object application, which is to create a solid base of shared resources available for any application needing them. Furthermore, limiting the scope to temporary objects contradicts the idea of storing reusable objects, which are typically permanent resources intended for long-term use.