Deleting rather than disabling components in Launch | Community
Skip to main content
P
philipk92120636
New Participant
March 17, 2021
Solved

Deleting rather than disabling components in Launch

  • March 17, 2021
  • 2 replies
  • 1532 views

Hi everyone!

Is there any performance benefit from deleting rules after disabling them? It's easy enough to filter out disabled components, but I wondered if the performance of Launch is compromised at all by having over 100 disabled rules and over 200 disabled data elements.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yuhuisg

Deletion helps with managing all of your Rules and Data Elements within Launch's UI. It has zero impact on your libraries. (Disabled Rules/Data Elements/Extensions are never included in libraries.)

2 replies

yuhuisg
yuhuisgAccepted solution
New Participant
March 18, 2021

Deletion helps with managing all of your Rules and Data Elements within Launch's UI. It has zero impact on your libraries. (Disabled Rules/Data Elements/Extensions are never included in libraries.)

Gokul_Agiwal
Gokul_Agiwal
New Participant
March 17, 2021

Once you disabled the rule or data elements they are not be in Launch main library so performance wise all good. So deleting the rule it's like other way round.

Terms & ConditionsAccessibility statement

Loading footer...