Question
LTI Mindtree
IN
Last activity: 18 Jul 2022 10:08 EDT
ActionAutoSubmit submitting all the assignments in flow
I have Assignment (A), configured a FlowAction with HTML ActionAutoSubmit, next I have a screen flow contains 3 Assignments and When I execute Assignment A is auto completing and the next screen flow assignments also auto completing which are supposed to complete on user action
with same below snapshots working properly in UI-kit application , whereas in Cosmos its not working with same flow and FA and ActionAutoSubmit
Sunlife
CA
@PrakashP6773I am facing same issue on similar configuration, let me know if you find any solution for this
Updated: 31 May 2022 3:39 EDT
LTI Mindtree
IN
Any leads/Suggestion , still we didn't get any work around for this.
Raised an SR too but they also not able to help arounds this.
Pegasystems Inc.
IN
Could you please share the SR number here?
LTI Mindtree
IN
INC-221695
Updated: 15 Jun 2022 12:03 EDT
Extend Health Inc
US
@PrakashP6773 We ran into the same issue in one of our flows. To resolve the issue we created a custom HTML section, copied the top half of the ActionAutoSubmit and made some minor tweaks, after doing this we have something that will auto submit but will not leave a lasting onLoad function.
here is the code we are using:
<SCRIPT>
<% ClipboardPage actionPage = pega.getUIEngine().getUIActionPage("finishAssignment");
pega.getUIEngine().getUIAction(actionPage).register(); %>
/*Setting a timeout to submit page automatically so the function is done onload without updating the onload event in the window*/
setTimeout(function(){
doSubmit();
pega.u.d.detachOnload(doActionAutoSubmit);
},500);
</SCRIPT>
hopefully this helps.
Maantic Inc
US
@AndrewM2378 thank you for sharing the code.
are you received this code from pega support team?
why existing HTML ActionAutoSubmit is not working? is any update are you received from pega support team?
if you have any related SR number share it
Updated: 18 Jul 2022 10:08 EDT
Extend Health Inc
US
@JohnPaulRaja,C no this code was updated on our team. Our issue was just as described by the @PrakashP6773 we had a subflow which would call ActionAutoSubmit which would cause our screenflow to auto-submit on the main flow after we had already finished the subflow. The existing HTML does not work for our use case because it creates an onload function that executes for any FA that comes after it runs. The code i posted instead calls that function one time. so it will not affect future FAs.