Question

Pro & Con of Collection over Activity

Using Pega 7.2.2

Please let us know the Pro & Con of Collection over Activity. If possible with scenario.

Any reference article or Link

Thanks in Advance

***Updated by moderator: Lochan to update platform capability***

Correct Answer
January 3, 2019 - 5:37am

Hi Rajasekhar,

Below link may help you to understand about collections. 

https://community.pega.com/knowledgebase/documents/understanding-collections-process-721

https://community.pega.com/knowledgebase/articles/pega-collections-technical-overview

Collections are more than just a list of rules to run. PFB are the benefits.

 

1. More logic can be represented in the collection rule.
2. Response actions( implement common patterns without activities) and function alias(Function aliases can be used to make form easier to read and define) support provide structure and extensibility making the rules easier to configure, understand and delegate.
3. Features like rule referencing, execution tracking and dynamic function parameters can be used to solve common rule engine requirement more elegantly.

Please review the below articles for more information:

https://community.pega.com/knowledgebase/articles/introduction-collections-feature-pega-7-platform
https://community1.pega.com/community/pega-product-support/question/collection-vs-activity
https://community1.pega.com/community/pega-support/question/pro-con-collection-over-activity

Thanks,

Viswa

 

 

 

 

Comments

Keep up to date on this post and subscribe to comments

October 10, 2018 - 4:10am

Hello,

I guess you already seen what the help file is presenting: Use a collection to model business logic and implement common rule engine patterns. Collections define an ordered sequence of rules, the conditions under which they execute, and post-processing steps known as response actions. The business-friendly options on this form help you to quickly develop flexible solutions that are easily understood by various audiences.

Creating a collection is like creating a service for your application I would say. So for example you know you have entries and in order to get the result back you need to call a specific set of rules in a dedicated order. This when a collection could be interesting.

You really need a specific business scenario I believe. Sorry if I wasn't clear enough.

 

October 11, 2018 - 10:17am
Response to MarcLasserre_GCS

Thanks Marc.

Gone through help and understand example you provided above.

Comparing {i.e. Pro & Con} of Activity and Collection. If you can help in getting comparison of Activity and Collection.

Best Regards....

October 15, 2018 - 6:00am
Response to RajasekharU0829

Well,

It is always a bit difficult to discuss the collection subject without a good business scenario.

But you cannot really compare an Activity with a Collection. An activity is usually set to achieve a specific task and set to call specific other activities for example.

Where you could have multiple collections using different activities on completely different order if you need to from one to another.

October 31, 2018 - 8:23am
Response to MarcLasserre_GCS

Thanks for your response. Can you please elaborate.....

January 3, 2019 - 5:12am

Regarding Pro & Con of Collection over Activity. Please share if you have any thing other then below help details

"Use a collection to model business logic and implement common rule engine patterns. Collections define an ordered sequence of rules, the conditions under which they execute, and post-processing steps known as response actions. The business-friendly options on this form help you to quickly develop flexible solutions that are easily understood by various audiences"

Thanks in Advance.........

January 3, 2019 - 5:37am

Hi Rajasekhar,

Below link may help you to understand about collections. 

https://community.pega.com/knowledgebase/documents/understanding-collections-process-721

https://community.pega.com/knowledgebase/articles/pega-collections-technical-overview

Collections are more than just a list of rules to run. PFB are the benefits.

 

1. More logic can be represented in the collection rule.
2. Response actions( implement common patterns without activities) and function alias(Function aliases can be used to make form easier to read and define) support provide structure and extensibility making the rules easier to configure, understand and delegate.
3. Features like rule referencing, execution tracking and dynamic function parameters can be used to solve common rule engine requirement more elegantly.

Please review the below articles for more information:

https://community.pega.com/knowledgebase/articles/introduction-collections-feature-pega-7-platform
https://community1.pega.com/community/pega-product-support/question/collection-vs-activity
https://community1.pega.com/community/pega-support/question/pro-con-collection-over-activity

Thanks,

Viswa

 

 

 

 

January 8, 2019 - 4:45am
Response to ViswanathReddy

December 12, 2019 - 9:43am

Benefits

Collections can be very useful in Business Rules Engine (BRE) projects or in the BRE portion of a BPM project. Potential uses include:

  • Defining and maintaining a list of adjustments that determine the cost of a loan or insurance policy
  • Defining and maintaining a list of decision rules that qualify or disqualify a loan dynamically, determining which rule caused the disqualification

While activities sometimes appear to be a natural, general-purpose and flexible way to create business logic, activities can quickly become complex to analyze, debug, and maintain. The Collections feature provides a better way to model the orchestration and process behind both simple and complex business rule logic.

 

https://community.pega.com/knowledgebase/articles/java-and-activities/introduction-collections-feature-pega-7-platform