93 results found

1. Navigator - lacking placement possibilities

   The current Navigator in Connect Designer is lacking in functionality compared to the Classic Studio in regards to placement possibilities.
   I always have the Navigator activated and when developing I prioritize canvas area left<->right and therefore I want the Navigator at the top, unfortunately this is not possible in the Connect designer (see picture from Classic Studio).

   •  

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

2. Get list of apps/users/user groups from hub

   It would be great to have a variable or a connector/API I could call and get a list of apps/users/user groups from hub/environments.
   (or few extra features such as sending invitation to a user via flow).

   Like in flow classic, see attached picture.

   If updating users are not available due to security reasons, but at least fetching a list of users would be great.

   •  

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

3. New FlowScript function for BI apps and other data driven apps

   For data driven apps or any BI apps it would be great to have an easy way to create a complex result set of data.
   With this function available we could create amazingly flexible and "Qlik-like" apps in no time.

   Let's consider one scenario.
   We want to display sales per period, per a few selected sales reps and products.
   As dimensions we have Period (Quarter/Month), Salesman, Product.

   For the actual sales we have one big fact table with all all sales, including the dimensions above.

   In an app we want to select a group of salesmen and a few product, and then display, sales per quarter.

   For this we need two operations (possibly in one FlowScript function):
   1. Combine
   2. Populate

   Combine: Create one table with all combined dimensions (like an outer join without a on/where clause)

   Populate: Map one (or more) columns from the fact table and put the aggregated result in the corresponding cell in the combined dimension table. Have a default expression for the cells without any value. This table would the be the output from the function.

   The output could then be used to display & update data in a effective and comprehensive way.
   Of course this can be done using existing FlowScript functions, but the suggested function would save a lot of time and have the potential to create a lot more flexible solutions.

   For data driven apps or any BI apps it would be great to have an easy way to create a complex result set of data.
   With this function available we could create amazingly flexible and "Qlik-like" apps in no time.

   Let's consider one scenario.
   We want to display sales per period, per a few selected sales reps and products.
   As dimensions we have Period (Quarter/Month), Salesman, Product.

   For the actual sales we have one big fact table with all all sales, including the dimensions above.

   In an app we want to select a group of salesmen and a few product,… 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  ·  Designer  ·  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

4. Add proper Report Print Layout configuration to Flow

   There is a need for proper Report Print Layout configuration. Must allow dynamic sizing of all cells in a table/layout, logo, formatting, conditions etc. Today's HTML is far to rigid. For some use cases the layout is so poor that we can't even use it internally, not to mention externally.

   Main need is for PDF, e.g. Word would have been nice, but less important

   Ideally there should be an engine on the backside, allowing to be automatically sent on E-mail or printed to predefined print.

   For IFS users, similar IFS Report Designer and Print Agent. The built in IFS tools are strong, but limited availability of data to be fetched into the report restricts the tool far too much.

   There is a need for proper Report Print Layout configuration. Must allow dynamic sizing of all cells in a table/layout, logo, formatting, conditions etc. Today's HTML is far to rigid. For some use cases the layout is so poor that we can't even use it internally, not to mention externally.

   Main need is for PDF, e.g. Word would have been nice, but less important

   Ideally there should be an engine on the backside, allowing to be automatically sent on E-mail or printed to predefined print.

   For IFS users, similar IFS Report Designer and Print Agent. The built in IFS tools… more

   4 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
   under review  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   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.

5. 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 that can be toggled on/off in the table portlet settings titled "Retain Row Selection" and "Auto-Refresh Post Workflow".

   When "Retain Row Selection" is turned on it will not deselect rows in tables, and when turned off (default) it will deselect the rows. When "Auto-Refresh Post Workflow" is turned on (default), it will automatically update or refresh the table data after running a workflow, and when off it will keep the same data as before clicking a workflow button. This could even be added down to the workflow level settings themselves

   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… 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  ·  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

6. Customized Button Placement in Clients

   The suggested improvements to the current system involve enhancing the user experience and customization options in the graphical user interface (GUI). The proposal includes two main features:

   1. Customizable Button Placement: The users express a strong interest in having the freedom to choose where the buttons (outputs) from user steps appear in the GUI. Currently, the system only allows the selection of priority, but the buttons always appear in the bottom right corner of the user step. The proposal seeks to provide flexibility, allowing users to position the buttons according to their preference, resulting in a more intuitive and user-friendly interface.

   2. Button Color Customization: Another requested feature is the ability to assign different colors to the buttons. For example, the proposal suggests using green for "go," orange for "pause," and red for "stop." By introducing this capability, the GUI can offer visual cues that align with the specific action associated with each button. This color customization enhances usability and clarity, making it easier for users to identify the intended functionality of the buttons at a glance.

   The suggested improvements to the current system involve enhancing the user experience and customization options in the graphical user interface (GUI). The proposal includes two main features:

   1. Customizable Button Placement: The users express a strong interest in having the freedom to choose where the buttons (outputs) from user steps appear in the GUI. Currently, the system only allows the selection of priority, but the buttons always appear in the bottom right corner of the user step. The proposal seeks to provide flexibility, allowing users to position the buttons according to their preference, resulting in a more intuitive and user-friendly interface.

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

   6 comments  ·  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
   under review  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   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.

7. Customizable Header/Banner Color in Portal 2

   In the current setup of Portal 2, users lack the ability to customize the color of the header/banner area, which limits the flexibility in aligning the platform's appearance with corporate branding or user preferences.

   Proposed solution is to introduce an option within the Style settings of Portal 2 that allows users to set a distinct color for the header/banner area. This feature should provide an intuitive color picker or the ability to enter hex codes, enabling precise control over the color scheme. This customization capability will enhance the visual appeal of Portal 2 and allow for better branding consistency, improving user engagement and satisfaction by providing a more personalized interface experience.

   In the current setup of Portal 2, users lack the ability to customize the color of the header/banner area, which limits the flexibility in aligning the platform's appearance with corporate branding or user preferences.

   Proposed solution is to introduce an option within the Style settings of Portal 2 that allows users to set a distinct color for the header/banner area. This feature should provide an intuitive color picker or the ability to enter hex codes, enabling precise control over the color scheme. This customization capability will enhance the visual appeal of Portal 2 and allow for better branding consistency, improving… more

   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
   started  ·  AdminMalin Johansson (Admin, Novacura) responded

   This request has been moved to the Flow Connect project and is under development.

8. Customizable Spacing and Border Controls for KPI Cards in Portal 2

   Requesting the addition of customizable spacing options between KPI cards in Portal 2. Currently, a gray KPI card is being utilized as a workaround for creating space between blue and green KPI cards. However, there is an inability to disable the border of this empty card. We propose the implementation of features that allow users to control spacing between KPI cards and provide the option to toggle borders on or off for improved layout flexibility.

   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

   0 comments  ·  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
   under review  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   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.

9. Add picture/thumbnails option to buttons

   It would be a nice feature if we could show pictures/logos in buttons (and not just unicode characters).
   Similarly to the new 'list input with picture' feature.

   •  

   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  ·  Clients (Webclient, Android, iOS)  ·  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

10. The possibility to handle errors in some connectors

    In some connectors for example FileSystem we need the ability to handle errors and sometimes ignore them.

    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

    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
    under review  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    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.

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

    •  

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

12. Close Pinned Steps

    A process involves calling a flow fragment with a pinned user step. After completing the fragment, returning to the main flow retains the now irrelevant pinned step, potentially causing confusion. Pinned steps should close along with their parent flow to avoid this issue.

    14 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

    under review  ·  5 comments  ·  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

13. Change name of Filter button PORTAL 2

    Be able to change the name of the Filter button on the Filter portlet.

    Example:

    •  

    7 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

    under review  ·  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

14. Enhanced Targeted Messaging Capabilities in Flow Server

    Requesting an expansion of the Flow Server messaging functionality to support targeted communication beyond global message sends to Portal. While acknowledging the utility of global targeting, there's a strong need for more precise messaging options such as targeting specific Flow user IDs, user roles, and user workflows. This enhancement would significantly empower communication in multi-user setups, providing greater flexibility and efficiency in message delivery within the Flow environment.

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

15. Change back symbols for arrays to []

    In current version of FlosScript {} symbol is used for declaring arrays(Pic A), inside IF and FOR loops(Pic B) and to showcase when Flowscript will be used(Pic C).

    I think, using same symbol for everything makes it's purpose unclear and can cause unnecessary confusion. Was change from [] to {} for array declaration cause by some real need?

    •  

    •  

    •  

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

16. Can items remain highlighted once clicked on them?

    Is there any way that when adding records for an employee, the name stays highlighted. After each record I enter, I have to re-click on the name to enter more or even see anything pertaining to the employee.

    the user wants the name to be able to remain highlighted while they are doing processes for named user until the processes are completed instead of having to click on the user name each time to create additional processes for them.

    •  

    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

    under review  ·  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

17. Return to parameter view from flow6 in Components

    New version of parameters for Components in counteractive and in opposition to Lowcode philosophy behind Novacura products. Frankly it looks unfinished, which I hope it is. Moreover in old version you were able to open used Component, which would be even more important now, when they are all dumped in one place and not divided into folders or even show which flows they are assigned to.

    •  

    •  

    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  ·  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
    under review  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    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.

18. More effortless usage of types with typed output everywhere

    Typed variables in Flow is a good thing, but most often it creates a lot of extra work to make it work.
    As many of the ideas here suggests, while FlowScript provides a lot of possibilities, it has in its current form made Connect come a bit too far from being Low-Code.

    To simplify the handling of types it would be of great help to be able to easily make sure that the output variables always are of the wanted and expected type.

    For example:
    - In a IFS DB Machine Step be able to easily ("low-codish") define types for the output data, both for a query and for a script.
    - In a data grid, be able to have numeric and date columns that is easy to format to the desired format and that always output the same type as the inputted type.

    Typed variables in Flow is a good thing, but most often it creates a lot of extra work to make it work.
    As many of the ideas here suggests, while FlowScript provides a lot of possibilities, it has in its current form made Connect come a bit too far from being Low-Code.

    To simplify the handling of types it would be of great help to be able to easily make sure that the output variables always are of the wanted and expected type.

    For example:
    - In a IFS DB Machine Step be able to easily ("low-codish") define types for… 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  ·  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
    under review  ·  AdminAndreas Berggren (Admin, Novacura) responded

    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.

19. Configure font color, size or bold/italics in Portal 2 Scheduler

    We would like to have an option to configure font color, size or bold/italics in Portal 2 Scheduler.

    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

    1 comment  ·  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
    under review  ·  AdminMalin Johansson (Admin, Novacura) responded

    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.

20. FlowScript Code Formatter

    Currently, Flow Script does not offer any assistance in code formatting, which could lead to less readable and harder to manage scripts.

    We suggest the introduction of a "Code Formatter" button in Flow Script. This button would apply some basic formatting rules, such as indentation, to make scripts more readable and easier to maintain. Even though users may request further customization options, having basic formatting support will be a significant improvement over the current situation.

    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  ·  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
    under review  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    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.