Question

After Local Action Submitted work is assigning to workbasket instead of current user

Hi all,

I have a screen flow. At the first assignment I have a local action. After local action is submitted, work goes to workbasket instead of current user.

How can I fix this routing problem?

Thanks in advance.

BR
Burak

***Updated by moderator: Lochan to update Categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
March 26, 2018 - 10:56pm

In Local action there is option called disable bulk processing, uncheck this.

Comments

Keep up to date on this post and subscribe to comments

March 23, 2018 - 4:29am

Hi Burak,

I have the same problem. If you will find a solutions, I will be wait for your reply.

Thanks a lot
Gokhan

March 23, 2018 - 6:06am

Hello,

Are you really talking about a "ScreenFlow" here ? Because a flow of type "ScreenFlow" should just be FlowActions calling each other and always routing to current operator running the flow.

So I don't quite see how you could have a local action and then be routed to a WorkBasket. Can you share few screen shots of your flow definition ?

March 23, 2018 - 9:23am
Response to MarcLasserre_GCS

Hi MarcLasserre_GCS

You can see the flows and screenshots in the attachment

BR

Burak

 

March 23, 2018 - 9:41am

Right,

So this isn't a ScreenFlow and router is custom. Apparently it is routing to current operator or to WorkBasket depending on incoming parameters.

I would guess, after having ran your local action, parameters are different and because of that routing to WorkBasket.

The best approach from here is to trace routing activity called "ToCurrentOperatorOrWorkBasket" in order to understand which parameter is missing and responsible for this.

March 26, 2018 - 10:56pm

In Local action there is option called disable bulk processing, uncheck this.