Question 2 Replies 124 Views × Close popover Arunkumar Velmurugan (A___K) Accenture Application Development Specialist Accenture NL View Profile Send Message A___K Member since 2018 20 posts Accenture Posted: July 16, 2019 Last activity: July 17, 2019 Posted: 16 Jul 2019 4:36 EDT Last activity: 17 Jul 2019 4:12 EDT Closed When would you create a component rather than an Organization Ruleset? Hi Team, Can you explain to me when we need to create a component instead of building the same feature in org level ruleset? Regards, AK Low-Code App Development × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Moderation Team has archived post, learn more × Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 1 year ago Posted: 16 Jul 2019 12:59 EDT × Close popover Marc Lasserre (MarcLasserre_GCS) PEGA Principal Software Solutions Engineer Pegasystems Inc. FR View Profile Send Message MarcLasserre_GCS PEGA replied to A___K Hello, Have you checked the HELP file? What is your Pega version? Posted: 1 year ago Posted: 17 Jul 2019 4:12 EDT × Close popover Arunkumar Velmurugan (A___K) Accenture Application Development Specialist Accenture NL View Profile Send Message A___K Accenture replied to A___K For example, I can build an email integration feature in Organization level ruleset. that can be used by all application build on that Organization Otherwise, I can build the same email integration as a component. I can add this component to all applications. So I need to know, In which scenario I need to create a component instead of creating a ruleset (to build).