Question
Accenture
IN
Last activity: 23 Sep 2016 0:33 EDT
Standards suggestion for a scenario at design level
Suppose i have an abstract class say "A-" and three concrete class "A-B", "A-C" and "A-D"
Now the requirement is on commit of these 3 work object i need to do some processing by running an actity.
Activity has been created in "A-" class.
Now i have a question, in which class declare trigger should be place to run the activity?
Approach 1:
Create one declare trigger in "A-"
Approach 2:
Create three declare trigger in three concrete class.
Which should be the best practice keeping performance factor in mind ?.
~Ross
***Updated by Moderator: Lochan. Removed user added helpme and Ask the Expert tags. Apologies for confusion, shouldn't have been an end-user option***
Pegasystems Inc.
FR
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.
Pegasystems Inc.
IN
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.
Accenture
IN
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 ?
Accenture
IN
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 ?
Accenture
IN
Any Suggestion or updates on this ?
Accenture
IN
Any Suggestion or updates on this ?
Accenture
IN
Any comments / discussion regading the performance aspects of the above scenario ?
Or Is just a matter of choice ??
Pegasystems Inc.
IN
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 ?
Accenture
IN
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