Question

Local action being executed when the Flow action's allow when condition fails

1) Create a sample case type with one stage and one step.
2) Create a sample flow action and a sample optional local action from that assignment of the first flow of the case type.
3) Configure "Never" as the condition for the flow action to get executed.
4) Create a sample case so that the case stops as the first assignment.
5) On executing the task, the optional local action is executed instead of the flow action. (Since we have configured "Never", it is expected that the flow action is not to be executed. But, instead of showing an information message saying that the user cannot perform the flow action due to access restrictions, the system executes the optional local action)
6) Expectation is that the system should show an information message saying that the user does't have access to perform the flow action. ( Note: This happens when the assignment doesn't have an optional local action to perform. This is expected to be displayed even when the assignment has an optional local action.)

Is this the expected behavior? Do we have a configuration point to overcome this?

Let me know if i am missing something.

Thanks in advance.

Correct Answer
July 28, 2018 - 4:46am

An SR was raised to address the above mentioned issue. But turns out that if an user doesn't have the access to perform the flow action from an assignment, an optional local action that flows out of that assignment will be executed.

Thanks for all the help.

Comments

Keep up to date on this post and subscribe to comments

Pega
July 16, 2018 - 7:11am

Hi,

How are you configuring step-3. Could you share the screenshot? 

I tried to reproduce the issue but seems it is working as expected at my end. Please find the document attached.

 

Pega
July 16, 2018 - 7:16am
Response to ranjr

By the way, i have used PRPC 7.4 to test this. In case if this is happening for some other version of PRPC, you could raise it as a bug to Pega.

July 16, 2018 - 11:48am
Response to ranjr

Hi Rajeev,

There is a slight change in the way you have tested things. I want you to set "Never" as the execute when condition for the flow action that goes out of the assignment and not on the optional local action. Once you set this, and then when you try to execute the task from the task link on the review harness, since you can't execute the flow action, the local action gets executed.

When you don't configure that local action, a message is displayed on the screen saying that the user doesn't have access to execute the flow action.

I want the same message to be displayed even when there is a local action configured. 

Please try this scenario and let me know.

July 25, 2018 - 2:36am
Response to Ratan

Hi Rajeev,

Can you try adding a privilege to that flow action .

July 28, 2018 - 4:46am

An SR was raised to address the above mentioned issue. But turns out that if an user doesn't have the access to perform the flow action from an assignment, an optional local action that flows out of that assignment will be executed.

Thanks for all the help.

November 12, 2018 - 11:14pm
Response to Ratan

Hi Ratan,

We have a similar situation in our project. Please let me know how you have handled this.

Thank you

 

September 16, 2019 - 9:40am

Is this issue solved?

September 17, 2019 - 3:34am
Response to vaspoz

Hi @vaspoz -

Hi,

Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.

You may also refer this discussion link as a reference in the new thread.

Vidyaranjan | Community Moderator | Pegasystems Inc.