Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Arunkumar Velmurugan (Arunkum@r)
Areteans Technology Solutions
Associate Architect
Areteans Technology Solutions
GB
Arunkum@r Member since 2018 29 posts
Areteans Technology Solutions
Posted: Jul 16, 2019
Last activity: Jul 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

To see attachments, please log in.
Low-Code App Development

Posted: 5 years ago
Posted: 17 Jul 2019 4:12 EDT
Arunkumar Velmurugan (Arunkum@r)
Areteans Technology Solutions
Associate Architect
Areteans Technology Solutions
GB

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).

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice