How to pass user to requested for in Flow Designer?

[Luiz Lucena]

Hi everyone, 

When Flow Designer was introduced I thought it was intended to facilitate, but instead I'm seeing many difficulties. 

The newest is below.

We have a catalog item which uses a variable set, this variable set is used in all catalog items we have, most of them using legacy workflow (which works perfectly).
The variable set contains user information as follow:
1. Affected User (u_requested_by)

2. Caller (opened_by)
etc. 

OOTB, the opened_by is being passed to the Requested For field in the RITM and SCTASK.

What we want is to pass the Affected User (u_requested_by) to the Requested For field, same as we do with all other catalog items using legacy workflow.

I saw other users having the same issue in the community and some of them solving by adding a new custom business rule which creates another issue, there are few BR's doing the same thing, how to solve this without having to create additional BR?

[Allen Andreas]

Hello,

Flow Designer has been out for several years at this point and it does work for majority of people. Your workflow, based on this scenario, is doing nothing special that a Flow can't do. With that said, you'd first want to use the Get Catalog Item Variables action to pull in the variables and their values, then you can use an Update Record action (however many needed) and use the pills (selections in the right-hand panel), etc. and set the value of the field as you need on those records with the variable value, etc.

The only piece here is timing and if this flow runs after the out of box process of setting that field on those records or not. So, try the above and see.

[Luiz Lucena]

Thanks, @Allen Andreas 

I tried, but still not working, I'm sure I'm missing something.

[Allen Andreas]

Hi,

I'm glad my initial reply was Helpful and is guiding you properly.

Please use Update Record action per my initial reply.

You'll need to specify the record that you're trying to update, then set the field values accordingly.

[Kirby R]

@Luiz Lucena Your table is sc_request. Shouldn't it be sc_req_item?