141 results found

1. FTP Connector in Connect

   To be able to communicate with FTP servers in Flow Connect. The FTP Connector can be used to upload and download files from an FTP server. It can also perform other operations such as creating remote directories and list files and directories on the FTP server

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Liquid & XLST Transformers for automations

   All ow automations to perform transformations on input and output for webhook triggers so we can support current classic customers in connect

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Integration  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. SFTP Connector in Connect

   To be able to communicate with SFTP servers in Flow Connect. The FTP Connector can be used to upload and download files from an SFTP server. It can also perform other operations such as creating remote directories and list files and directories on the SFTP server

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   planned  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   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.

4. Scheduler Portlet in Connect

   Support for the Scheduler Portlet in Novacura Flow Connect

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   started  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   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.

5. Generic Database connector with ODBC

   A generic database connector that can connect to any database for which an ODBC driver is available

   Databases that we can Connect to via ODBC
   IBM Db2 (all variants)
   MySQL / MariaDB (MySQL Connector/ODBC, MariaDB Connector/ODBC)
   PostgreSQL (psqlODBC driver)
   SQLite (SQLite ODBC driver)
   SAP HANA (SAP HANA ODBC driver)

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Allow Client messages to display for Flowscript step

   Since Flowscript is so powerful now we can put extensive Scripts/loops in the script. If we do that in a userflow we cannot tell the user what's happening, because currently we have no way to add a client message like in other steps. Would be nice if we can get a flowscript function to add messages at different steps of the script execution. Otherwise UX for long running processes will be poor (missing user feedback)

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Infor M3 Connector (NOT REST based)

   In Flow Classic, we have two connectors associated with M3. One is the REST based connector, the other is connector to older versions of Infor M3. In Flow Connect, we would like the same capabilities from Classic. Currently, only REST based connectors for Infor M3 are available.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Push refresh of portlet

   Have an option from an app/component to send a refresh command to a portlet for a specific user.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Make it possible to have the same app in many different menus.
   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Designer  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. On-Premise (onprem) Runtime

    Some customers need to run Flow Connect on their premises (on-prem) for different reasons.

    1. Data requirements – Strict data security/privacy/legal requirements where the data is not allowed to leave the premises. For these types of customers, it is essential that everything runs on-prem since they don’t want any connection to the outside networks.
       Some examples:
       • Aerospace & defense
       • Defense manufacturing
       • Healthcare
       • Government and public sector

    2. Low-latency requirements - Some customers have low-latency requirements with systems handling a high volume of transactions/executions. Typically, their existing infrastructure/external systems are already on-prem due to the exact reason. For these types of customers, flow connect adds a roundtrip through the cloud to access the data that’s already in their premise. This adds to the latency. It would be beneficial for this customer category to avoid the roundtrip through cloud infrastructure and be able to access their data locally.
       Some examples:
       • High volume manufacturing
       • Retail
       • E-Commerce

    3. Intermittent connectivity – some customers do not have stable, always available internet connectivity due to the nature of the work they do. This does not mean they are not connected to internet at all. Rather internet connectivity is not a guarantee. Even if the internet is available, it might not be stable or with very low bandwidth. These customers want to carry on their work while being offline and once they are connected to internet, they want to sync their data/transactions/executions. We can divide this into two subcategories depending on how long they are disconnected from internet.
       a. Short term disconnection
       Typically, the disconnect from the internet lasts from a few hours to a few days. Examples include service technicians who goes into the field to carry out his work, field operations, mobile service units, etc.

    b. Long term disconnection
    The disconnect is long-term ranging from few months to a year or so. Example includes mining & oil rigs, fishing & maritime, engineering & construction sites, etc.
    Suggested approach
    The section below describes the approach RnD could take on handling some of the use cases/requirements mentioned above. It’s also important to note that the suggested approach will not cover all the requirements and use cases.
    RnD wants to avoid taking a big-bang approach, but instead take a step-by-step approach where we solve one problem at a time and build on it. This would allow RnD to get feedback on the first step before moving on to the next steps.
    Definitions & Disclaimers
    • Design Time – The part of Flow Connect where the application packages/apps/components are designed and deployed to different environments. Design time also includes defining the connector configuration for the apps. So, Flow Hub, Flow Designer, and Portal Designer falls under design time. Please note that in the suggested approach the design time will always be in the cloud.

    Stage 1 – Online on-prem
    This solution involves running some parts of the Flow Connect runtime on the customer's local network. This lets Flow apps run machine steps directly on local systems without needing to connect to the internet/Novacura Cloud. The Internet is still needed to login to the flow connect client and to download the Application packages, apps, and components. However once logged in and loaded, the execution will be routed through the customer's local network. The following diagram illustrates the flow of data with this approach on a high-level.
    Suitable for:
    • customers with low-latency requirements - since the execution occurs locally it is an efficient solution.
    Limitations:
    • As mentioned previously, Design time will be always cloud only.
    • Internet is still needed to authenticate with Novacura Flow Connect and download app packages/apps/components/modules/configurations.
    Out of Scope
    • On-prem design time
    • Web client on-prem (web client delivered from a local on-prem service)
    • Integrations

    Stage 2 – Runtime on-prem
    Stage 2 builds on top of Stage 1 where more services run on the customer's site. The goal of this step is to run flow connect apps without the need to communicate with the Novacura cloud. With this solution,
    • Users will be able to authenticate themselves locally
    • App packages/apps will be delivered from a service running on-prem
    • Execution of machine step will be 100% on-prem (modules and connector configurations delivered from a local service)
    Suitable for:
    • Customer who wants their apps to work without being connected to the internet for a longer period (Long-term intermittent connectivity).
    • Customers who do not want any of their data to be exposed outside.
    Limitations:
    • Design time is still cloud only.
    • Data can be updated on-prem but no syncing back to cloud is allowed.
    • An internet connection is needed occasionally to be able to receive updates from the Novacura cloud.
    Out of Scope
    • On-prem design time
    • Integrations
    Considerations
    Although stage 2 looks very appealing it is an inherently complex solution with many unknowns (the diagram is an oversimplification). It will require a significant amount of work and time to fully implement for production level. There are many unknowns when it comes to different services that will require their own PoC before starting to implementation.

    Offline client
    Offline functionality makes it possible to work with flow apps without an internet connection for a short period of time. For offline functionality to work it is required that the data needed to execute apps are downloaded beforehand. With offline functionality all transactions that are produced by the apps while offline are put in a queue. Then The transactions are executed automatically in the background when the device has internet access.
    Suitable for:
    • Field operations, service technicians, etc. who are disconnected from the internet time to time. (short-term intermittent connectivity).

    Summary
    • Customers who want everything on prem will not be covered with the suggested solutions since design time will always be in the cloud.
    • Customers with Low-latency requirements will be covered with Stage 1 of the proposed solution.
    • Customers with Long-term intermittent connectivity requirements can be covered with Stage 2 of the proposed solution. However, it is a huge undertaking with a lot of unknows parts.
    • Customers with Short-term intermittent connectivity requirements will be covered with offline client functionality.

    Some customers need to run Flow Connect on their premises (on-prem) for different reasons.

    1. Data requirements – Strict data security/privacy/legal requirements where the data is not allowed to leave the premises. For these types of customers, it is essential that everything runs on-prem since they don’t want any connection to the outside networks.
       Some examples:
       • Aerospace & defense
       • Defense manufacturing
       • Healthcare
       • Government and public sector

    2. Low-latency requirements - Some customers have low-latency requirements with systems handling a high volume of transactions/executions. Typically, their existing infrastructure/external systems are already on-prem due to the exact reason. For these… more

    22 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    planned  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    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.

11. 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 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Designer  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Allow Alias for datasources

    I noticed that the Prefix are not working on the SQL query on the flow
    
    script when I use the module.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Designer  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Uptime dashboard

    Why
    As a customer, I would like to have a traffic light/dashboard to view my system's uptime and identify any outages in my region.

    What
    This does not have to be observability in the form of who ran what app and when. Rather, I just want to get the dashboard to confirm that my system is up and running, and also to view its historical data. Similar to what AWS or Microsoft have. Or qlik: https://status.qlikcloud.com/

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Public User

    Public user is used in Classic for external users (customers etc) to book appionmetns using a workflow (a link is sent out in email/sms)

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. OAuth2 Client Credential authorization in FlowHUB APIs

    There are some cases when I'd call FlowHUB API from a workflow/automation and there is no way to use interactive authentication (machine-to-machine cases).

    It would be great to implement OAuth2 Client Credentials for these cases.

    With this option we could develop applications to maintain FlowHUB (e.g.: fetch users by group, invite users, move apps, generate bundle, etc).

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Hub  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Improve screen transitions

    There is an issue with screen transitions in both Flow Classic and Connect. Currently, users scan a barcode into a text input field using a scanner. After scanning and selecting "Next," the input field remains active, allowing users to continue scanning or typing even while the query is executing. This behavior is consistent across both Flow Classic and Connect.

    Ideally, once a barcode is scanned and the transition or query is triggered, the input field should be locked or disabled to prevent further input until the process completes. This would help avoid confusion, as users might mistakenly believe that multiple barcodes are being processed, even though only the first input is considered. This behavior was demonstrated in a screen recording, where after the initial scan and screen transition began, the field still accepted input before the process was completed.

    There is an issue with screen transitions in both Flow Classic and Connect. Currently, users scan a barcode into a text input field using a scanner. After scanning and selecting "Next," the input field remains active, allowing users to continue scanning or typing even while the query is executing. This behavior is consistent across both Flow Classic and Connect.

    Ideally, once a barcode is scanned and the transition or query is triggered, the input field should be locked or disabled to prevent further input until the process completes. This would help avoid confusion, as users might mistakenly believe that multiple… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Bring Your Own Identity Provider

    In Flow Connect, we would like to be able to use other identity providers to login. For example, we would like to be able to login via OKTA instead of Microsoft.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Additional text in the cards in the calender

    In the visual planning in the old portal we are able to see more text in the cards. Is it possible to fix the same feature in Connect?

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Portal  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Overview/details change when running in Analytics/Automations

    In Flow Connect Hub:

    When looking in Analytics/Automations you can see the status of the scheduled automations which is great.

    However when a job is during "running mode" you get a lot of lines with each step. My proposal is that you only have one line in the overview for each job and display it in status "Running". Then if you want the details you can click to the right to see details. I don't think details for running jobs are very important - just to see the overview better.

    See attached img. Marked lines are all the same job in "running mode".

    In Flow Connect Hub:

    When looking in Analytics/Automations you can see the status of the scheduled automations which is great.

    However when a job is during "running mode" you get a lot of lines with each step. My proposal is that you only have one line in the overview for each job and display it in status "Running". Then if you want the details you can click to the right to see details. I don't think details for running jobs are very important - just to see the overview better.

    See attached img. Marked lines are all the same job… more

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Voice Step

    Using voice as input when executing a task is becoming increasingly more useful and also more requested, with the use of AI.

    To make this experience smooth and seamless we would need a voice step which automatically or on demand (by pressing a button) starts a recording. The recording can be paused or stopped (or auto stopped after a defined number of seconds of relative silence). The recoding is then returned to the workflow and can be processed in the following steps, using AI.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  AI  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating