Skip to main content

What is the purpose of being able to enable/disable process actions in a role? The reason asking is that when one action is not enabled, the whole process flow is not granted and therefor not working.

Here an example situation:

Example of a simple process flow

There is a table task on several screens which all execute the same type of action and flow to opening a report. For management it is easy to have all entries in the same flow.

In a role only one or limited screens need to be available to the user, so only those parts of the flow need to be accessible I would think. Lets say the first line in the example and not the Pink and Green marked ones.

Another consequence is when you are developing and adding a new screen with the same task and you add it to the flow. Let say the Green marked one. Now in all role that have this flow, the functionality is broken, because there is a new action available even though that would not touch anything in the old roles. You need to enable this action in the flow to make it work again.

The example situations are in my opinion valid reasons to go limit the process flow, but this seems not possible. Am I missing something which makes the control of action access in a role useful?

INFO:

Platform: 2023.3
Universal GUI: 2024.1.13.0

Indicium: 2024.1.12.0

Hi Mark,

You indeed need to have rights on all user actions of a process flow to have the process flow granted.

As a developer, you cannot individually assign rights to process actions, their availability is implicit based on the rights of the object and action the process action represents.

The idea behind this is that, as a user, you need to be able to perform all of the actions in the process flow further down the line.

When a process flow has multiple start actions, it would indeed be nice to be able to partially grant the process flow, only granting ‘chains’ in the process action which are fully granted. This would require availability of the starting process action and all potential subsequent process actions.

Feel free to post an idea for this in the ideation section.

 

Alternatively, a more complex process flow with multiple starting points could be modeled as a subflow and reused in multiple process flows that represent the various starting points. There is an idea already posted for this:

 

Terms & ConditionsCookie settings