Assignment error when calling a flow on pyWorkCover of child case
When attempting to call a flow on the pyWorkCover page of a child case object, we are getting the following error: 'Either no actions are specified for this assignment or you do not have the permission to access any of them'
The child case was created from a sibling under the same parent transaction. We used the pxAddChildWork on the pyWorkCover to create the child case.
Calling this same flow and process works if the child work object was created through the parent transaction calling the subcase, as opposed to using the pxAddChildWork from the sibling.
Accepted Solution
PEG
IN
check for pyTemporaryObject property is true/false in both the scenario's. If it is false, we can see the child work object without errors.
In my local, I changed to false and worked fine.
Hope this helps!
Pegasystems Inc.
IN
Hi
When exactly the issue is coming ? Are you trying to perform some sort of refresh while doing this ?
Accenture
US
In the sibling child case, we have an 'other actions' menu item to create the sibling case. This option calls a flow in modal dialog using the pyWorkCover page. Inside this flow we have a flow action/section for the user to enter values that will be used for the new child case. After the submit of the flow action, we call a utility shape with pxAddChildWork using the child case work class as the ChildClass and pyStartCase as the flowName.
PEG
IN
Hi ,
I tried to implement the similar use case in local 7.2 instance. However I'm seeing some other related issues.
Could you please clarify which class name pyWorkCover page belongs to?
And also please verify in clipboard parent flow is exists or not in pyWorkPage-> pxFlow after launching the Flow in Modal dailog and perform actions i.e. invoking pxAddChildCase.
Accenture
US
Hi Gangababu,
The pyWorkCover class is the parent transaction class which the first child gets created under. In my specific application the class is TC-CN-Work-Transaction. The child case is TC-CN-Work-PRF.
No, the parent flow does not exist inthe child case's pyWorkPage-> pxFlow list, after creating it with pxAddChildWork. The only flows on the pyWorkPage is the current flow the child is in, and the pzInternalCaseFlow.
Thanks,
Tom
PEG
IN
Hi Tom,
I have created scenario like below. Child1 and Child2 are sibling's.
Parent:
Gang-gangaapp-Work -> StartMyFlow, StartMyFlowNew
Child1:
Gang-gangaapp-Work-Teacher-> StartChildFlow
Child2:
Gang-gangaapp-Work-Student->StartChildFlowNew
I am running StartMyFlow and from other actions, I have invoked StartChildFlow to create child case.
Under StartChildFlow , I have configured button to launch "FlowInModalDailog". In FlowInModalDailog, I am invoking other flow from parent StartMyFlowNew which has some action followed by invoking pxAddChildWork. Inside pxAddChildWork, I am invoking StartChildFlowNew to create child case.
Kindly correct me if I miss any steps to replicate the issue.
When I run the StartMyFlowNew flow standalone child work object is created successfully, however when I launch from FlowInModalDailog, child work object gets created and wasn't able to open the created work object. Getting error.
Hi Tom,
I have created scenario like below. Child1 and Child2 are sibling's.
Parent:
Gang-gangaapp-Work -> StartMyFlow, StartMyFlowNew
Child1:
Gang-gangaapp-Work-Teacher-> StartChildFlow
Child2:
Gang-gangaapp-Work-Student->StartChildFlowNew
I am running StartMyFlow and from other actions, I have invoked StartChildFlow to create child case.
Under StartChildFlow , I have configured button to launch "FlowInModalDailog". In FlowInModalDailog, I am invoking other flow from parent StartMyFlowNew which has some action followed by invoking pxAddChildWork. Inside pxAddChildWork, I am invoking StartChildFlowNew to create child case.
Kindly correct me if I miss any steps to replicate the issue.
When I run the StartMyFlowNew flow standalone child work object is created successfully, however when I launch from FlowInModalDailog, child work object gets created and wasn't able to open the created work object. Getting error.
|
PEG
IN
Could you please confirm launching the flow would create the child case rather than launching from "Flow In Modal Dialog"?
Accepted Solution
PEG
IN
check for pyTemporaryObject property is true/false in both the scenario's. If it is false, we can see the child work object without errors.
In my local, I changed to false and worked fine.
Hope this helps!
Pegasystems Inc.
IN
Hello
Thanks for the details. We have to try to do a similar kind of design at our end to verify the behavior. Will get back to you with my observation.
Meanwhile others can comment if they can share any thoughts on this.