Impact on having too many unpublished applications in an environment

Hi,
One way to limit the amount of inactive/unpublished applications is to use a dedicated deployment application. Instead of creating an application for every patch, you can just re-use a single application and flush out the objects before each use. This may make it harder to trace objects to a particular patch, but it will reduce the amount of inactive/unpublished applications sitting in your environment.

You can also go through and delete older applications.

jeremys . I know how to maintain and what should be done to avoid creating too many applications. My questing is very much focused to " impacts for having too many (500 +) inactive applications ?"

The impact is more around doing things like updating CDTs. In previous versions (would need to verify on later ones 18+), objects in applications were inspected. So, the more you have, the longer the impact analysis and update took.

The impact is more around doing things like updating CDTs. In previous versions (would need to verify on later ones 18+), objects in applications were inspected. So, the more you have, the longer the impact analysis and update took.