We have one reusable flow which we are trying to call from navigation rule. Based on parameter, flow logic will be different. But it seems there is no OOTB to pass parameters to flow when calling from navigation rule.
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Share this page
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.
Posted: 7 years ago
Posted: 18 Jul 2015 4:04 EDT
Phani Sahukaru (sahup1)
Architect - Financial Services
As per our requirement, we have multiple options in navigation. On click of each option, a flow will run. Since screens for multiple case types are similar, so we have planned to create a single flow. And whenever there is deviation from normal behavior we will circumstance sections based on parameter received from navigation rule.
So I think suggested approach will not work.
Below is one more approach.
When we use createNewWork option in navigation, in backend one of the OOTB function- CreateNewWork will get called. Since this function is enhanced in pega 7 to pass parameters, we tried to use similar function in custom JS and referred in harness.With this we are able to call flow from navigation but there are some syntax issues in passing parameters
Syntax "¶m1=value1" while passign value to parameter 'flowParams' is not working.
We have copied function CreateNewWork from file pega_desktop_api. Please share if you have any idea on this.
Posted: 6 years ago
Posted: 4 Feb 2016 0:05 EST
revanth gajjala (revanthg)