Flow Designer set to capture variables but not working for standard users

[Tim Sanders]

Hi everyone,

I set up a Flow to capture all of the Catalog Item variables and pass them to the SCTASK when it gets generated.  It works perfectly for me (a system administrator), but when everyone else puts in a ticket, it doesn't pass any of the variables to the SCTASK.  I have no idea why this would be the case as it feels completely contrary. 

Scenario 1: Standard user submits request, variables do not pass to SCTASK in the Fulfiller view.  Neither Fulfillers nor sys admin can see variables in the SCTASK.

Scenario 2: System admin submits request, variables do pass to the SCTASK in the Fulfiller view.  All Fulfillers and sys admin can see the variables in the SCTASK.

Why would the system behave this way?

Thanks,

Tim

[AnveshKumar M]

Hi @Tim Sanders 

Check how the flow is running, I mean who is the run as user for the flow. Whether it is System User or the User who initiated. If it is user initiated change it to system user.

Open the flow and from the menu select flow properties to check this.

 

 

[Tim Sanders]

Thank you Anvesh for your reply! 

I just made the change in my Flow and when I went to test it, it generated the RITM, but it did not generate the SCTASK.  That's certainly not a behavior I expected.

I am assuming that, if the Properties were set to "User who initiates session" then they would have to have a specific role, but I don't want to grant more roles than absolutely necessary.

[Tim Sanders]

It appears that there was an error when it ran.  According to the Executions Details page, it states that "Operation failed with error: com.snc.process_flow.exception.Op  Exception: The requested operation was prohibited by security rules."

I'm not certain what security rules these may be, so I'll keep digging.

[AnveshKumar M]

Hi @Tim Sanders 

It is because of ACL issue only.

Just cross checking, have you activated the flow after changing the properties (In your screenshot I see Activate button still no grayed out)? If not, please do that and try again, because if the flow is running as system user this error should not pop.