Hello,

I think I would use the same approach as the Trigger called pxTrackStatuses which is at Work- level. So I would say A- level, it will also be easiest to maintain. 

Hi

For each Declare Trigger rule, the Pega 7 Platform monitors database operations for objects of the Applies To class (and concrete classes derived from that class). So you can keep it in A- level.

Thanks Las and Santanu for the reply,

Since "the Pega 7 Platform monitors database operations for objects" creating three triggers would means monitoring three triiger, which would not be advicable from performance perspective, right ?

Actually i wanted to list down the demerits of creating declare triggers in three class.

One obvious one is that if a new class A-E comes then we have to create another declare trigger in A-E class.

As asked in the last reply, will creating declare trigger in three concrete class affects performance ?

Any Suggestion or updates on this ?

Any Suggestion or updates on this ?

Any comments / discussion regading the performance aspects of the above scenario ?

Or Is just a matter of choice ??

Hi

As I said earlier, for each Declare Trigger rule, the Pega 7 Platform monitors database operations for objects of the Applies To class (and concrete classes derived from that class). So you can keep it in A- level. Why you have to crate three triggers ?

It has been suggested to me that keeping it at child class, wil boost the performance.

So was trying to understand the performance aspects of bothe approach

So that i can have the pros and cons of both the approach

~Ross