Has anyone tried skipping the Go Button in assignment
Thanks
What do you mean by “skipping”? The go button is what opens the assignment itself, so I assume you are trying to do something like deep link to the assignment directly? So the user opens the form directly?
Yep after moving from one assignment to another , I dont want the Go button screen . I tried this code from pzConstellation Control. But the javascript is not working alert(“1”);
var oSafeURL = new SafeURL(“@baseclass.pzUpdateClipboardOnConstellationCaseFlowUpdate”);
alert(“2”);
oSafeURL.put(“portalName”, pega.u.d.portalName);
oSafeURL.put(“assignmentId”, assignmentID);
oSafeURL.put(“isInCreateStage”, false);
alert(“3”);
alert(oSafeURL.toURL());
pega.u.d.convertToRunActivityAction(oSafeURL);
alert(“4”);
pega.util.Connect.asyncRequest(
“POST”,
oSafeURL.toURL(),
{
success: function(o) {
alert(“Success”);
},
failure: function(o) {
alert("Failure " + o.status);
}
}
);
alert(“5”);
You only get the “go” button when moving from one assignment to another IF the next assignment is not assigned to the current user.
So why not just assign “step 2” to the current user so that it auto-opens. This is how Pega natively “skips the go button” in your configuration
Hi Marc this is a screen flow how do I assign this
Rgds
Balaji Choda
OK, I think I understand - this is a common issue.
The simple answer
Multi-step/Screenflow assignment is done here
The longer answer
I believe, you have assigned to a queue or another user? Like this
So, the routing decision for a screenflow is a single decision, it is not dynamic. Once you have made that choice, each step in the screenflow is routed using that logic.
So, as a result, the user who continues through this will always get the “go” button screen.
This is a very common question asked, you can see various responses:
Personally, I prefer to have a single assignment in the Queue (workbasket) that is basically “assign to me”, then the Multi-step form triggers next (screenflow), that is assigned to current user.
Infinity '26
Watch this space. As I said, this is one that has been raised before, I know there will be some changes coming in this space. 
Another option worth trying is to use post-processing to update the assignment for the next step to the user who completed the current assignment.
With this approach, once the user completes a step, the post-processing activity updates the next assignment’s operator. As a result, the assignment is effectively parked with that user rather than remaining in the work queue, allowing them to continue through the subsequent Screen Flow steps without needing to re-pick the work item.
It may not be suitable for every use case, but it’s a practical workaround if the goal is to keep the flow with the same user after they pick it up from the queue.
Give it a try and let us know how you get on.
Refer to this post which outlines how to reassign the assisgment Re-assign Screen flow to another user | Support Center?