54 results found

1. Dynamic List of Values in Clients

   It would be great to have two separate List Selections in a User Step. These list selections should impact each other such that what I select in List Selection 1 would change what is seen in List Selection 2. This is possible in 2023.3 Portal, but this functionality is needed in the Android, iOS and webclient.

   48 votes

   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

   7 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and is now available to all users on Flow Connect. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

2. HTML to PDF Connector

   HTML to PDF connector is a frequently used connector for designing and generating PDF reports in Flow Classic. Additionally, it's also possible to merge existing pdfs with this connector.
   As mentioned in this idea https://ideas.novacura.com/forums/956630-novacura-flow-connect/suggestions/48235034-add-proper-report-print-layout-configuration-to-fl
   The design capabilities of the existing connector are somewhat limited/rigid. Ideally, it should be far easier/flexible to design a report layout in connect. Here are some options we can consider for HTML to PDF connector in Flow Connect.

   Option 1

   Can be divided in to two sub sections.
   a. Report design as its own step in the designer – The idea of this is to have a new “report designer step” that is a low-code/WYSIWYG editor. With this approach, the flow developers do not design the report with HTML rather use the editor to design. So even someone who does not know HTML can design a report.

   Advantage – Flexible, feature rich design capabilities with no HTML knowledge needed.

   Disadvantage – Migrating existing customer flows with HTML to PDF connector in Flow Classic to this new format might be challenging.

   b. Generate PDF report as a client feature – Once we have figured out a way to design the report, the PDF generation can happen in the client-side. This would enable offline PDF generation since we do not need to communicate with the Flow Connect backend for PDF generation.

   Advantage – Offline PDF Generation. No connector setup is needed to design & generate reports.

   Disadvantage – If the PDF’s are too big (in size) it will affect the performance of the client. especially in mobile/handheld devices with limited memory capacity. Might have an effect on battery life as well.

   Option 1.a & 1.b are mutually exclusive. We can stop with option 1.a where a new design step that keeps the PDF generation server-side. Or we can have the existing report design machine step but have option 1.b to generate the PDF on the client side.

   Option 2

   Keep HTML to PDF connector as it is – We can also have the exact same functionality of the HTML to PDF connector in connect. So, a connector configuration is needed design & generate PDF reports as PDF generation is happening server-side. With this approach we can borrow lot of stuff from Flow classic (e.g. the design of the machine step) and reuse the existing connector infrastructure.

   Advantage – Migration from Flow Classic to Connect will be easier. Also, since its server-side pdf generation, the connector should be able to handle relatively bigger PDF files.

   Disadvantage – We will continue to have the same issues as it was in Flow Classic. (e.g. Rigid/lack of design capabilities, formatting & logos, no offline printing, etc..)

   Option 3

   Use a third-party service like ConvertAPI. Convert API also provides dedicated servers if needed.

   Advantage – Already available and easy to setup with the existing REST Connector.
   Access to other documents formats like DOCX,XLS,XLSX, TXT,JPEG.
   Relatively easy migration from Flow Classic.

   Disadvantage – Since its REST service hosted by a third-party 3rd party privacy terms apply.
   Lack of on-Prem hosting options (e.g. Convert API does not provide any onprem hosting solution)

   HTML to PDF connector is a frequently used connector for designing and generating PDF reports in Flow Classic. Additionally, it's also possible to merge existing pdfs with this connector.
   As mentioned in this idea https://ideas.novacura.com/forums/956630-novacura-flow-connect/suggestions/48235034-add-proper-report-print-layout-configuration-to-fl
   The design capabilities of the existing connector are somewhat limited/rigid. Ideally, it should be far easier/flexible to design a report layout in connect. Here are some options we can consider for HTML to PDF connector in Flow Connect.

   Option 1

   Can be divided in to two sub sections.
   a. Report design as its own step in the designer – The idea of this is to… more

   •  

   37 votes

   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

   3 comments  ·  Connectors  ·  Delete…  ·  Admin →
   completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and is now available to all users in Flow Connect. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

3. Scrolling in Workflow Elements Locked when Workflow is Not in Edit Mode

   When double clicking an included workflow in studio to view what parameters are being sent, the scroll bar is locked unless the user is in “edit” mode.User should be able to scroll and view all the parameters without entering edit mode or resizing the window.

   26 votes

   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

   4 comments  ·  Designer  ·  Delete…  ·  Admin →
   completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and is now available to all users in Novacura Flow Connect. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

4. Translation panel and standard buttons

   Support for multiple languages in Flow can be a involved process and with many large workflows in a solution it can be challenging to provide a consistent translation (and terminology!) in your apps. In the translation industry, a common way to work is to have a side-by-side or spreadsheet view of all text with the original language on one side and the translations on the other. I would love it if the Languages tab in Environment could collect all text from one or multiple apps and then put that text in a table with editable fields where you can enter translations. That would both make translating an app easier and faster (since you don't have to click through lots of User steps and Buttons) and make the translations themselves better and more consistent since you could cross-reference all the text in the app.

   In addition, it would be really helpful if you could configure a set of "standard" buttons in your environment where you can set translations but also make sure buttons use the same terms throughout an environment. When all buttons are free text, it's easy to end up with apps where some buttons say "OK", others say "Next", "Continue" etc. although they do the same thing in concept (move forward in the app). From an UX perspective, apps with more consistent buttons look more professional. We did something similar in some RISE apps where we call a fragment containing a table of standard button texts which works fine, but it would be even better if you could select a Standard button from a dropdown (with one selection obviously being free text).

   Support for multiple languages in Flow can be a involved process and with many large workflows in a solution it can be challenging to provide a consistent translation (and terminology!) in your apps. In the translation industry, a common way to work is to have a side-by-side or spreadsheet view of all text with the original language on one side and the translations on the other. I would love it if the Languages tab in Environment could collect all text from one or multiple apps and then put that text in a table with editable fields where you can enter… more

   •  

   20 votes

   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  ·  Delete…  ·  Admin →
   completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications in Connect using the Phrasebook. We hope you enjoy using it.

5. Import portal 2 translations

   Ability to import translations from portal 2 into portal connect.

   16 votes

   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  ·  Delete…  ·  Admin →
   completed  ·  AdminOla Carlander (Admin, Novacura) responded

   We are pleased to announce that the requested feature has been achieved via a workaround available to all users. The workaround is described at the end of the Flow Script training (https://appcademy.novacura.com/ - free sign up) under the "Migrate Portal 2 translations" chapter.

6. AD Sync (SCIM) for Flow Connect

   System for Cross-domain Identity Management (SCIM) is a set of application-level protocols that use JSON, REST, and several different authentication methods to automate the task of user provisioning. This will allow Admins to configure Azure to create, update, and delete users seamlessly from Azure AD to Novacura Flow Connect without the need of manually doing this within the Hub.

   15 votes

   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  ·  Delete…  ·  Admin →
   completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

7. Better Offline Data Caching

   Today, a customer can download offline data. But if the app crashes, or the user in the field (who is offline) makes changes and then app crashes or they quit out by accident, its confusing to the user as to what has been completed. To the user, it feels like the data has been lost.

   An example, lets say I have an offline flow which downloads 10 records in a table. While offline, I add 2 new records to that table, and go to the next step. If the app crashes when the app reopens, and the flow is rerun, the user will only see the 10 records. Not knowing they submitted the 2 additional records. This could be true if they quit out of the app by mistake, instead of the app crashing.

   Today, a customer can download offline data. But if the app crashes, or the user in the field (who is offline) makes changes and then app crashes or they quit out by accident, its confusing to the user as to what has been completed. To the user, it feels like the data has been lost.

   An example, lets say I have an offline flow which downloads 10 records in a table. While offline, I add 2 new records to that table, and go to the next step. If the app crashes when the app reopens, and the flow is rerun,… more

   15 votes

   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

   5 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

8. NiceLabel Connector for Connect

   Utilize the old connector for integration with Nicelabel. Currently the workaround is to use the REST connector or FileSystem connector to communicate but it could require an automation server or additional set up to consume messages in the file system directory.

   14 votes

   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  ·  Connectors  ·  Delete…  ·  Admin →
   completed  ·  AdminAlbin Lundberg (Product Owner, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

9. Diagnostic Mode in TEST and PROD Environments

   As a customer there are small changes between TEST and PROD environments. It would be nice to be able to run diagnostic mode against a TEST environment and see the errors that one might get there with variables.

   14 votes

   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  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   completed  ·  AdminOla Carlander (Admin, Novacura) responded

   We are pleased to announce that the requested feature has been fully developed and will be available to all users very soon. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

10. 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)

    13 votes

    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  ·  Connectors  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

11. Global Functions for Cross-Script Usability in Flow Environment

    We request the implementation of a feature that enables users to create global functions within the Flow environment. These global functions should be accessible and usable from any script within the environment, irrespective of their location. By having the ability to define reusable functions at a global level, users can avoid redundancy and promote code modularity across their workflows. This enhancement would significantly improve the efficiency and maintainability of scripts within the Flow environment.

    12 votes

    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  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed in Novacura Flow Connect and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it when you upgrade to the new version of Flow Connect.

12. Allow Developer to Open a Fragment Without being in Edit Mode

    We would like to open up a fragment from the editor instead of either needing to enter edit mode or search in the server content window. There are times when multiple fragments of the same name exist in the server, and it becomes important to know which version is actually used. Furthermore, editing fragments, and not committing or reversing changes causes lock out of apps - all just to open an fragment to inspect.

    12 votes

    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  ·  Designer  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users in Novacura Flow Connect. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

13. 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 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 →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

14. Using flow properties in the initialization & cleanup commands in Oracle database connector

    This will enable the following scenarios that is possible in Flow classic.

    1. User impersonation via initialization command in Oracle database connector
    2. Set default language of a user

    •  

    11 votes

    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  ·  Connectors  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

15. File System Connector

    File System Connector to replace File System Connector in Flow Connect to replace 60% of the most used operations in Classic File System.

    11 votes

    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  ·  Connectors  ·  Delete…  ·  Admin →
    completed  ·  AdminIrshad Hassan (Admin, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it. Product Documentation

16. Parameterized IN Syntax for SQL Statements

    Change Improvement Request: Support Parameterized IN Syntax for SQL Statements

    Title
    Support parameterized IN clause syntax to avoid dynamic SQL execution

    Background / Current Behavior

    Currently, when building SQL queries that require filtering using an IN clause with multiple values, the only practical solution is to dynamically construct the SQL string and execute it using EXEC(@query).

    Example:

    DECLARE @query NVARCHAR(MAX)

    SET @query = '
    SELECT *
    FROM Orders
    WHERE OrderId IN (' + @OrderIds + ')
    '

    EXEC(@query)

    This approach requires stringifying the entire query, which introduces several issues:

    Reduced readability and maintainability

    Increased risk of SQL injection if not carefully handled

    Poorer query plan reuse

    Harder debugging and logging

    Proposed Improvement

    Introduce support for built parameters that can expand into an IN clause using syntax similar to:

    WHERE OrderId IN ({OrderIds})

    Where {OrderIds} represents a parameter containing a list/collection of values that the engine expands safely into parameterized values.

    Example usage:

    SELECT *
    FROM Orders
    WHERE OrderId IN ({OrderIds})

    With input parameter:

    OrderIds = [101,102,103]

    Internally this could be translated into something equivalent to:

    WHERE OrderId IN ({OrderIds})

    Expected Benefits

    Eliminates the need for dynamic SQL (EXEC(@query))

    Improves query safety and reduces SQL injection risk

    Enables better query plan reuse

    Improves readability and maintainability

    Makes multi-value filtering consistent with other parameterized queries

    Change Improvement Request: Support Parameterized IN Syntax for SQL Statements

    Title
    Support parameterized IN clause syntax to avoid dynamic SQL execution

    Background / Current Behavior

    Currently, when building SQL queries that require filtering using an IN clause with multiple values, the only practical solution is to dynamically construct the SQL string and execute it using EXEC(@query).

    Example:

    DECLARE @query NVARCHAR(MAX)

    SET @query = '
    SELECT *
    FROM Orders
    WHERE OrderId IN (' + @OrderIds + ')
    '

    EXEC(@query)

    This approach requires stringifying the entire query, which introduces several issues:

    Reduced readability and maintainability

    Increased risk of SQL injection if not… more

    9 votes

    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

    2 comments  ·  Connectors  ·  Delete…  ·  Admin →
    completed  ·  AdminOla Carlander (Admin, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

17. 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

    9 votes

    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  ·  Connectors  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

18. Scheduler Portlet in Connect

    Support for the Scheduler Portlet in Novacura Flow Connect

    9 votes

    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  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

19. Offline Data in Flow Connect

    Similar to Flow Classic, Customers will need the ability to download data locally to their devices in Connect and execute on that data. Once connected back to the internet, the information should be sent back to Novacura without user interaction.

    9 votes

    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  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.

20. Enhanced Search Result Details in Web NG Client

    In the current Web NG client, when users perform searches, the results do not indicate the menu under which each workflow is located. This lack of contextual information can lead to confusion, especially when multiple workflows have identical or similar names but reside in different menus.

    Proposed solution is to improve the search functionality within the Web NG client to include additional details in the results, specifically the menu location of each workflow. This information should be displayed clearly beneath the workflow name in the search results. Providing this contextual detail will help users quickly identify the correct workflow, reducing the likelihood of errors and improving navigation efficiency within the client. This enhancement will significantly enhance user experience by making search results more informative and actionable.

    In the current Web NG client, when users perform searches, the results do not indicate the menu under which each workflow is located. This lack of contextual information can lead to confusion, especially when multiple workflows have identical or similar names but reside in different menus.

    Proposed solution is to improve the search functionality within the Web NG client to include additional details in the results, specifically the menu location of each workflow. This information should be displayed clearly beneath the workflow name in the search results. Providing this contextual detail will help users quickly identify the correct workflow, reducing… more

    7 votes

    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  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    completed  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    We are pleased to announce that the requested feature has been fully developed and is now available to all users in Flow Connect. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.