Question
Creditone
IN
Last activity: 29 Aug 2019 2:31 EDT
How to Calling Flow in Work- from Split for Each my Page in Data- Class
Hello,
I have a requirement where I have to created assignemnts based on pagelist in split for each. That's all done. I used Split-For-Each and based on the pageList property I'm not able create creating assignments when i checked tracer it is showing error assignement error. But the problem is my Page property is in Data- class which is fine and the flow(Let suppose its A) that I'm calling from Split-For-Each is in Work-. Flow A inturn used Split join and calls other flow which are also in Work-. So I cannot save A into Data-.
Please suggest me how to call the flow (Work-) from Split-For-Each based on Page Property (Data-).
***Edited by Moderator Marissa to update platform capability tags****
Accepted Solution
Ernst & Young LLP
MT
When you use split-for-each on a .PageList() which is of a data class, the referenced flow must be in that data class. It's just because when split-for-each is executed by PRPC, the current iteration of .PageList() becomes the primary page/content page of the referenced flow. As the class of primary/context page is that Data class, rule resolution will never look for your flow in work class.
Solutions:
1. Move your flow (and relevant rules) from your work class to that data class.
Downside: none of the OOTB flow components (send email, post to pulse etc.) will work as all such activities are defined in Work-Cover- or Work- class, and your flow context page is of a data class. You need to create wrapper activity in your data class to invoke them on pyWorkPage/Top page.
2. Replace that data class with a work class (this is a dirty workaround though)
Pegasystems Inc.
US
Hi,
I haven't tried this personally, however the below developer help article sounds like it could be useful:
Hope this helps!
-Kurt
Accepted Solution
Ernst & Young LLP
MT
When you use split-for-each on a .PageList() which is of a data class, the referenced flow must be in that data class. It's just because when split-for-each is executed by PRPC, the current iteration of .PageList() becomes the primary page/content page of the referenced flow. As the class of primary/context page is that Data class, rule resolution will never look for your flow in work class.
Solutions:
1. Move your flow (and relevant rules) from your work class to that data class.
Downside: none of the OOTB flow components (send email, post to pulse etc.) will work as all such activities are defined in Work-Cover- or Work- class, and your flow context page is of a data class. You need to create wrapper activity in your data class to invoke them on pyWorkPage/Top page.
2. Replace that data class with a work class (this is a dirty workaround though)