Impact on having too many unpublished applications in an environment

RE: Impact on having too many unpublished applications in an environment

laurenc20 — Wed, 03 Oct 2018 14:32:55 GMT

I am not aware of and major downside to having unpublished applications. It would make sense as to have your objects grouped together in a logical way. A downside could be slowness during certain system processes.

RE: Impact on having too many unpublished applications in an environment

ChristineLHutchison — Wed, 11 Jul 2018 18:00:14 GMT

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.

RE: Impact on having too many unpublished applications in an environment

subhankarb — Tue, 10 Jul 2018 05:23:13 GMT

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 ?"

RE: Impact on having too many unpublished applications in an environment

jeremys — Tue, 10 Jul 2018 04:32:38 GMT

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.