26 results found
-
Enhanced Logging for Import Errors of OData Connector
Users encounter an issue when changing connectors for a specific flow. Currently, when an operation result indicates a failure, it is challenging to pinpoint which step within the flow has encountered the issue. As a result, users are compelled to manually review each step to identify the failed ones, causing unnecessary delays and frustration.
9 votesWe regret to inform you that this feature request has been declined. After review, our Product team determined that it does not align with our current product roadmap, particularly as Flow Classic is scheduled to reach end of life at the end of this year.
We appreciate your continued feedback and encourage you to keep sharing your ideas and suggestions with us.
-
As a user, I want the Batender connector to support the 64-bit version of BarTender, as it currently only works with the 32-bit version of
As a user, I would like the Bartender connector to add functionality for the 64-bit version of BarTender, as it currently only supports the 32-bit version of BarTender 2016 R8 (Automation or Enterprise Automation Edition).
4 votesI’ve reached out to the customers I know are using the BarTender connector. Based on the feedback I received, integrating with BarTender through its REST API or other available integration options should meet their needs. I’m therefore closing this suggestion.
-
Dynamic Data in Pinned Steps
One of the greatest challenge on any mobile client is the amount of data to present vrs available space to do that. It can be completely solved by using pinned steps which requires a bit of space from the top of the screen only.
What is tricky, however, is how to store the data that changes/is added dynamically along with User Steps that user goes through. So that every time a pinned step is triggered, it's updated with a new data from the most recent User Step. It is possible to do that but requires a rather complex work-around which…
4 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
GitHub Integration for Flow Studio
Currently, Flow Studio allows developers to view the XML code of their workflows by pressing F7, but there is no direct way to integrate these files with GitHub for version control and code storage, only server side in the Flow Server.
Proposed solution is to implement a direct integration feature between Flow Studio and GitHub, as an alternative to Flow version management. This feature would enable users to seamlessly push the XML files of their workflows directly to a GitHub repository from within Flow Studio.
4 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Ability To Insert Variable Into Priority For Buttons
The proposed feature centers on enabling developers to incorporate variables into the priority settings for buttons. This means developers can assign dynamic priority values to buttons based on contextual factors, such as user interactions, screen content, or application states. The platform will use these variable priorities to determine the order in which buttons appear on the user interface.
4 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Issue with Saving and History for Flow Connect
…I encountered issue with Flow Connect Designer that, in my believe, can cause issues in future. I’m testing flows for client and as I open it had some errors. I added debug step and committed (lets call it v2) to test. After a while I realized that previous commit (lets call it v1) did not have errors. Somebody worked on that flow before me, saved it but not committed. Now, looking through flow history it looks like my commit (v2) caused errors. A bit similar issue can arise when importing flow. We can import flow, work on it, run it2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
API Documentaion
Hi When we create a machine workflow and want to expose them via API. A documentation integration like swagger would be nice to have an overview and specification of the APIs. Instead of going to the flow right click generate web link and there we see what are the inputs and endpoint
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Enable picking Arrow type
In my example part "get CompanyTbl" was disconnected from flow of app, there is no input "sequence arrow". Despite this it's connection transformed into "data arrow" without any input form my side ant part's output is still available. It might cause issues while developing if developers have less control on process. Please give back ability to chose type of arrow or at least add prompt that type switch is occurring.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Allow the use of "join" syntaxes in flow script modules
I noticed that the Join are not working on the SQL query on the flow
script when I use the module.2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Enhanced Concurrent Sessions in Portal Connect
Portal 2 experiences performance issues when executing long-lasting queries across multiple tabs simultaneously, leading to excessive server load. Unlike Flow Client and Studio, which handle concurrent platform usage more effectively, Portal 2 struggles with this multi-tab functionality. This issue needs to be addressed in the upcoming Portal Connect to ensure smoother operations and better resource management.
Proposed solution is to implement a more proactive approach to managing queries in Portal Connect. This should include mechanisms to optimize and balance server load when multiple queries are run in different tabs by the same user. Consider introducing features such as query prioritization,…
2 votesThe backend for Flow Connect is significantly different from Flow Classic, with performance being one of our main areas of improvement. We have introduced features like running the client in the browser and added caching layers. Further enhancements will be made in the future based on user requirements and feedback from Flow Connect users.
We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Search and asset filtering (Flow Connect Conference 2024)
Search: currently we can search on all items inside the applications section in Hub. If you have any suggestions where else global search should reach, please let us know below!
Assets filtering: currently, only assets can be filtered. Should we add tagging and filtering to other places? Let us know below!
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Toggles to Retain Table Row Selection and also Refresh Table in Portal 2
When selecting a row or row(s) in a portlet table and then starting a workflow, the row selected is no longer showing as (gray) selected, making it hard to find what row was just worked with and pulled into the workflow. This may not always pertain to selected rows because some are actually deleted or removed from a portlet table.
However, a good addition would be to allow for tables in Portal 2 to deselect/not deselect the row and to allow the table to automatically update/not update the table after completing or closing a workflow. These are possibly some things…
2 votesThis functionality is already supported by the Table portlet. Configure the primary key setting to ensure the selected row remains selected after an action is performed.
-
Advanced Flow Name Search Options in New WebClient
In the new web client, the current flow name search allows filtering by typing a partial name. However, we would greatly appreciate additional search options such as "wildcards," "starts with," "ends with," and "contains." These enhancements would enable more refined searches, specifically allowing users to locate flows that begin with a certain pattern, end with a specific string, or contain a particular sequence. Implementing these features would significantly improve the flow discovery process, increase user productivity, and enhance the overall user experience in the web client.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Empowering Precision and Control with MidpointRounding in Flowscript's Rounding Process
Empowering Precision and Control with MidpointRounding in rounding processes with two conventions
1. Rounding away from zero
2. Rounding to nearest even2 votesWe regret to inform you that this feature request has been declined. It can be acomplished with a flow script module, for example:
function roundAwayFromZero(value: number) {
if value >= 0 {
return floor(value + 0.5);
}
return ceil(value - 0.5);
}
function roundToEven(value: number) {
let lower = floor(value);
let fraction = value - lower;
if fraction < 0.5 {
return lower;
}
if fraction > 0.5 {
return lower + 1;
}
if lower == floor(lower / 2) * 2 {
return lower;
}
return lower + 1;
}
assert roundAwayFromZero(2.5) == 3;
assert roundAwayFromZero(-2.5) == -3;
assert roundToEven(2.5) == 2;
assert roundToEven(3.5) == 4;
assert roundToEven(-2.5) == -2;
-
Option for Mobile Client Auto-Logout on Idle Time
Implementing an auto-logout feature for a mobile client on idle time is a common security measure to protect user data and privacy
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Workflow Datasource Ordering in Portal
When listing workflows for data source in e.g. a table Portlet, the ordering is appearing randomly. Ideally, a selected workflow should be on top and the remaining preferably ordered alphabetically by name given in Studio.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
This is done differently in Flow Connect; the data sources are sorted based on the application package.
-
Possibility to extract week number from a date
Could you add to DateTime module possibility to extract week number from a date in script? Like in std .net: System.Globalization.ISOWeek.GetWeekOfYear(DateTime.Now).
1 voteWe would like to inform you that this feature request has been declined as a workaround was presented under the comments section.
-
Better Agent Traffic Management
As a customer, I would like to be able to push a certain amount of traffic to an agent within an agent group. As an example, I can have 2 agents in an agent group for prod. When updating Agent 1, before updating Agent 2, I would like to push 75% of the traffic to Agent 1. This would allow me to see that the Agent is working adequately before updating Agent 2.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Numeric input with plus- and minus-buttons
Especially for mobile clients would be useful if we would have numeric input with plus- and minus-buttons. Input need to have minimum and maximum values, with possibility to set button increase value. Example for inputting hours: minimum hour registration is 15min with 15min increase and maximum hours 8
Control setup:
Min value: 0.25
Max value: 8
Step value: 0.251 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Configurable Client Timeout
I would like to be able to configure a timeout in the client such that if the client is inactive for a specified period of time, the client will logout. As an example, at Cash Checkout if the screen has not been touched for 4 minutes, the app should logout and request a re-login. This should be a configuration.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
- Don't see your idea?