Question

1
Replies
190
Views
DANNYR66 Member since 2016 8 posts
SERENDEBYTE INC
Posted: December 26, 2018
Last activity: January 11, 2019
Closed

Flow without attached to a Case does not get Called in Mashup

Hi All - Can anyone help on the below

Requirement - Need to execute a flow not attached to a Case.

Scenario 1) :

I have a parent case : Org-AppName-Work-A-B for which case is created and a process attached to it . In the Mashup code this process is getting called which is expected behaviour

Scenario 2) :

Extended this parent class to have a child class , Org-AppName-Work-A-B-C for which there is No case in Case Management but have created a regular flow under this class In the Mashup code this flow is not getting called but calls the pyStartCase flow of the parent eventhough the names of both the flows do not match which is NOT expected behaviour . Need to create a temporary WO with no case ids generated . Have selected the create Temp Object also have selected Skip Create Harness

Tried the below 2 options in Mashup but still does not work

1)

data-pega-action ='createNewWork'

data-pega-action-param-classname ='Org-AppName-Work-A-B-C'
data-pega-action-param-flowname = 'flowNameforthisClass'

data-pega-action-param-harnessname = 'New'
data-pega-action-param-model ='Modelforthisclass'

2)

data-pega-action ='OpenWorkByURL'

data-pega-action-param-classname ='Org-AppName-Work-A-B-C'
data-pega-action-param-harnessname = 'New'
data-pega-action-param-model ='Modelforthisclass'

data-pega-action-param-query ='pyActivity=Org-AppName-Work-A-B-C.OpenTestFlow'

Within the OpenTestFlow activty have a step to call the flow

Call NewFromFlow

params :

InsClass : Org-AppName-Work-A-B-C

FlowType : flowNameforthisClass

HarnessType : New

In both the above scenarios this flow is not getting called but calls the pyStartCase flow of the parent even though the names of both the flows do not match which is NOT expected behaviour

Regards,

Danny

***Edited by Moderator Marissa to update platform capability tags****

Case Management Data Integration
Moderation Team has archived post
Share this page LinkedIn