When you are using a screenflow, you can not route your assignment to other operator work list or workbasket. You need to come out of the screen flow and then as part of the main flow you can route it to workbasket.
Hello Kouhei, I would recommend staying in the Harness designed for a screenflow arena. https://pdn.pega.com/sites/pdn.pega.com/files/help_v719/procomhelpmain… PerformScreenFlow has the other actions link you mentioned you needed for example. Could you mention the business goal for what you are mentioning on the change stage? The change stage is available as a element to include in the UI for a screen flow. Are you in the screen flow would like to jump out without completing and move to a certain wrapup stage on the calling flow?
Hello Kouhei, Thank you for the information. In 7.1.6 I can see PerformScreenFlow included pyActionArea which intern hold pyActionArea right which control the display of Other Actions by the when condition : myParamPage.pyDisplayMode = 'ActionMenuBar'. I would suspect you might need to update the sequence to ensure the parameter is set. Also, I would suspect you could have a descision shape in your screen flow checking a parameter that maybe the approver could set via a local action or a screen flow field then if parameter set trigger a call the the smart shape change stage. (I haven't had a chance to test this Idea)
The router there can only be used to route to worklists, if you need the item to sit in WorkBasket until picked up by someone (i.e. getnextwork) then you would need to follow the approach in the linked article you posted.
The comment on the article is incorrect, this will produce an error for WorkBasket routing.