Settings and activity
19 results found
-
5 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
An error occurred while saving the comment 
Johannes Steger
supported this idea
·
-
3 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Johannes Steger
shared this idea
·
-
1 vote
The feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
Johannes Steger
shared this idea
·
-
3 votesJohannes Steger
supported this idea
·
-
1 voteJohannes Steger
shared this idea
·
-
9 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Johannes Steger
supported this idea
·
-
12 votes
We are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
An error occurred while saving the comment Johannes Steger
commented
Another great feature would be to be able to design ONE workflow that is online AND offline, not an online AND an offline version as you need to do today.
Meaning certain data is cached (we need to be able to identify the steps that do this) and automatically refreshed in a configurable intervall. when the user runs a workflow the client should recognize wether it's online or offline and depending on the status either fetch the data online or use cached data. Same would go for any machine steps that execute IFS logic.Johannes Steger
supported this idea
·
-
5 votesJohannes Steger
supported this idea
·
-
1 voteJohannes Steger
shared this idea
·
-
3 votesJohannes Steger
supported this idea
·
-
5 votesJohannes Steger
supported this idea
·
-
1 voteJohannes Steger
shared this idea
·
-
4 votesJohannes Steger
shared this idea
·
-
8 votesJohannes Steger
supported this idea
·
-
12 votesJohannes Steger
supported this idea
·
-
43 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Johannes Steger
supported this idea
·
-
22 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Johannes Steger
supported this idea
·
-
3 votesJohannes Steger
supported this idea
·
-
14 votes
An error occurred while saving the comment Johannes Steger
commented
I think in general it would be good to have the ability to update/change/delete a specific pinned step, meaning you can cross-reference the same pinned step from early in the flow again later in the flow.
Currently the only way to update a pinned step is if you run by that very same step again in the flow. In larger flows it can get quite cluttered with pinned steps while some contain irrelevant information for the current step.
Would allevate the functionality so so muchJohannes Steger
supported this idea
·
At the moment if we want to edit rows in the datagrid this is only possible with an extra pop-up window per line. This is very bad UX in the majority of our used cases. In the webclient it's possible to edit inline, so it would be nice to get that possibility in the client as well.
The most common use case we have over and over is a list of material where we just want to change the quantity. With the pop-up per line this becomes very inefficient.