Question

2
Replies
71
Views
Vipin Keshri (VipinK17)
Accenture LLP
Lead System Architect
Accenture LLP
IN
VipinK17 Member since 2013 17 posts
Accenture LLP
Posted: May 9, 2017
Last activity: May 16, 2017
Posted: 9 May 2017 20:23 EDT
Last activity: 16 May 2017 14:29 EDT
Closed

High CPU time consumed by GetFlowDataDefaults OOTB rule in Pegasurvey - Purpose / Solution / Workaround

hi team,


Based on client's requirement we created many survey screenflows using questions and subflows. We are using TabbedScreenFlow and TabbedScreenFlow7 across our application screenflows. When we had 1-4 level of subflows it was working fine, not much CPU time consumption. When we have added many more flows for the additional surveys with growing business requirement, we are seeing flows nested deep to a level of 8 or 10. The problem is now with the GetFlowDataDefaults - it is OOTB pega survey activity called from GetFlowData which finally gets called when calling Perform activity. It is taking >40 secs to iterate over the entire shapes in the PRIMARY and all the NESTED subflows.


For e.g. below shows 5 level of nested screenflows


Flow1 - Question, Question, Question, SubFlow1, Question, SubFlow2


SubFlow1 - Question, SubFlow3, SubFlow4


SubFlow3 - Question, Question, SubFlow5


SubFlow6 - Question, SubFlow7, Question


SubFlow7 - SubFlow8, SubFlow9,


My question is following:


1. Why do we have "GetFlowData" and "GetFlowDataDefaults". What feature does it provide?


2. What is the impact if we disable this feature by creating dummy version of that rule in our ruleset?


3. Is there any other work around to solve this issue?

Show More

hi team,

Based on client's requirement we created many survey screenflows using questions and subflows. We are using TabbedScreenFlow and TabbedScreenFlow7 across our application screenflows. When we had 1-4 level of subflows it was working fine, not much CPU time consumption. When we have added many more flows for the additional surveys with growing business requirement, we are seeing flows nested deep to a level of 8 or 10. The problem is now with the GetFlowDataDefaults - it is OOTB pega survey activity called from GetFlowData which finally gets called when calling Perform activity. It is taking >40 secs to iterate over the entire shapes in the PRIMARY and all the NESTED subflows.

For e.g. below shows 5 level of nested screenflows

Flow1 - Question, Question, Question, SubFlow1, Question, SubFlow2

SubFlow1 - Question, SubFlow3, SubFlow4

SubFlow3 - Question, Question, SubFlow5

SubFlow6 - Question, SubFlow7, Question

SubFlow7 - SubFlow8, SubFlow9,

My question is following:

1. Why do we have "GetFlowData" and "GetFlowDataDefaults". What feature does it provide?

2. What is the impact if we disable this feature by creating dummy version of that rule in our ruleset?

3. Is there any other work around to solve this issue?

4. We have used both TabbedNavigation and TabbedNavigation7 harness in our screenflows. Will it cause any issue?

Regards,

Vipin

***Updated by Moderator: Marissa to update categories***

Show Less
Pega Customer Service Low-Code App Development Case Management System Administration
Moderation Team has archived post, 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.