Home > Forum > User Voice > "Waiting for sub workflow" step shouldn't check the type of the user license

"Waiting for sub workflow" step shouldn't check the type of the user license UNDER REVIEW
1

MVP

Hi,

it would be great, if the "Waiting for sub workflow" step wouldn't check the type of the user license.

Imagine the following use case:

There's a parent workflow which is used by a few users and a child workflow used by all users of a company.
The users of the parent workflow have an Unlimited-Solutions Access License.
The users of the child workflow have a Single-Solution Access License.
After the parent started a few child workflow and is in the "Waiting for sub workflow" step.
Once the child workflows are completed the parent workflow should move on.
This works fine, if the user completing the child workflow has an Unlimited-Solutions Access License. If the user has a Single-Solution Access License the error "No Single Solution license for the user." is thrown.

We worked around this by:
- Moving the child workflow to a system step, if the user has only a Single-Solution Access License.
- The step has a 1 minute timeout, which will then move the child workflow forward to the intended step.

I've the following issues with this:
- The the error itself is correct, it's misleading because it's caused by the parent workflow.
- It's very likely that this issue will only encountered in the production environment.
- It introduces an unnecessary complexity to the child workflow.

WEBCON Version 2025.1.1.105

I've copied the license labels from:
https://community.webcon.com/posts/post/licensing/356/10

Best regards,
Daniel

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.