Settings and activity
12 results found
-
5 votes
An error occurred while saving the comment Morgan Moonan supported this idea · -
6 votesMorgan Moonan supported this idea ·
-
2 votesMorgan Moonan shared this idea ·
-
5 votesMorgan Moonan shared this idea ·
-
15 votesMorgan Moonan supported this idea ·
-
21 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.
Morgan Moonan supported this idea · -
48 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.
Morgan Moonan supported this idea · -
7 votesMorgan Moonan supported this idea ·
-
40 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.
Morgan Moonan supported this idea · -
10 votesMorgan Moonan supported this idea ·
-
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.
Morgan Moonan supported this idea · -
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.
Morgan Moonan supported this idea ·
Being able to pull the metadata workflow name or the workflow ID has been something we've been looking for for some time. Right now, we can only extract the name by building a script/program outside of Novacura Flow that extracts the data from the XML files, but having this available through the Flow Server connector will be must easier and faster.