7 results found

1. 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 →
   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.

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

   8 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 →
   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  ·  AdminOla Carlander (Admin, 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.

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

   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

   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. OPC UA connector in Connect

   he OPC UA connector allows Flow Connect apps to communicate with OPC UA servers

   3 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 →
   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.

5. Option to search in translations tab

   There is currently no search option to filter the columns in the Translation tab

   2 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 →
   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.

6. Enabling online/offline versatility

   Our framework is currently stringent in how to work offline: you download your sources (like in the morning), start working (deliberately offline) and your transactions are synced as soon as you are back online.
   In many circumstances Flow users in service do not know whether they will have internet while working though and they work offline foregoing on many advantages of being online.
   Ideally, we would have a variable available in our start variables (like DeviceId and ClientType) so that in the flows we can take different paths depending on whether the user has internet or not - analog to driving with google maps: you start online, Google recognized the connectivity is lost but keeps navigating in offline mode (so no trafffic info for example), and when you are back online you switch back to that mode

   Our framework is currently stringent in how to work offline: you download your sources (like in the morning), start working (deliberately offline) and your transactions are synced as soon as you are back online.
   In many circumstances Flow users in service do not know whether they will have internet while working though and they work offline foregoing on many advantages of being online.
   Ideally, we would have a variable available in our start variables (like DeviceId and ClientType) so that in the flows we can take different paths depending on whether the user has internet or not - analog to… 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

   3 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  ·  AdminMalin Johansson (Admin, 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.

7. Allow developer to connect one flow to multiple buttons in Portal 2

   We would like to use the same flow for multiple buttons in Portal 2. We use the input table to drive what the buttons do. Therefore, we would like to have that functionality in Portal 2 to connect one workflow to multiple buttons. Today, I need to duplicate the workflow to connect one button to one workflow. This adds unnecessary maintenance.

   2 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  ·  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.