70 results found

1. Tablet and Mobile Optimization for Portal 2

   Portal 2's current interface and interaction design do not cater effectively to tablet and mobile devices, presenting challenges for users on these platforms due to the lack of touch-friendly navigation and responsiveness.

   The enhancement focuses on redesigning Portal 2 to be fully optimized for tablet and mobile devices. This entails revising the user interface to ensure that all elements are easily navigable via touch interactions. Key considerations include increasing button sizes, ensuring that dropdown menus and other interactive elements are easily selectable, and implementing responsive design principles so that the layout adjusts dynamically to fit various screen sizes and orientations. This optimization aims to provide a seamless, intuitive user experience for Portal 2 users across all touch devices, thereby increasing accessibility and usability on tablets and mobiles.

   Portal 2's current interface and interaction design do not cater effectively to tablet and mobile devices, presenting challenges for users on these platforms due to the lack of touch-friendly navigation and responsiveness.

   The enhancement focuses on redesigning Portal 2 to be fully optimized for tablet and mobile devices. This entails revising the user interface to ensure that all elements are easily navigable via touch interactions. Key considerations include increasing button sizes, ensuring that dropdown menus and other interactive elements are easily selectable, and implementing responsive design principles so that the layout adjusts dynamically to fit various screen sizes and orientations.… more

   25 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

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

   •  

   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

   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.

3. Facilitate debugging of offline flows in flow studio

   Currently, the inability to run offline flows in debug mode in Studio complicates development and testing, significantly increasing development time. Resolving this issue soon will streamline the process and improve efficiency

   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

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

4. New Web Designer (Flow Connect Conference 2024)

   A fully web-based designer. No longer needing to download a thick-client to utilize the Flow Studio. Instead, just open it up in a web browser. Let us know if you have any ideas for the new web designer for Flow Connect!

   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  ·  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
   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. Property Types in Flow Connect

   In Flow Studio, users have access to various property types such as variables, tables, and more, which enhances flexibility and functionality in workflow creation and management. However, in Flow Connect, this capability is limited as users can only create properties as variables without any specific type assignment. This limitation reduces the utility and adaptability of Flow Connect, especially for users transitioning from Flow Studio who expect similar functionality.

   Proposed solution is to expand the property type options in Flow Connect to include a range of types similar to those available in Flow Studio. Introducing diverse property types like tables, lists, and more, alongside variables, will allow for more complex data handling and manipulation within workflows. This enhancement will align Flow Connect more closely with the capabilities of Flow Studio, ensuring a seamless experience for users and providing them with the tools needed to construct and manage workflows effectively and efficiently.

   In Flow Studio, users have access to various property types such as variables, tables, and more, which enhances flexibility and functionality in workflow creation and management. However, in Flow Connect, this capability is limited as users can only create properties as variables without any specific type assignment. This limitation reduces the utility and adaptability of Flow Connect, especially for users transitioning from Flow Studio who expect similar functionality.

   Proposed solution is to expand the property type options in Flow Connect to include a range of types similar to those available in Flow Studio. Introducing diverse property types like tables, lists,… 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

   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

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

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

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

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

8. Create Component from part of an App

   Typically when developing an App or a set of Apps, you don't exactly know how the Apps will end up and it is difficult to have a clear component strategy from the start.

   It would therefore be super helpful to be able to take a part of an app, a sequence of workflow elements, and turn that into a component when needed. Directly from the Designer.

   Preferably the function should be smart enough to suggest required input to the component.

   When created, the selected sequence of workflow elements should be replaced automatically by the newly created component.

   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

9. Group Values in Datagrid

   The datagrid should have a grouping header to make it easier for end users to find where the exact data they are looking for.

   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

10. GitHub Integration for Flow Studio

    Currently, Flow Studio allows developers to view the XML code of their workflows by pressing F7, but there is no direct way to integrate these files with GitHub for version control and code storage, only server side in the Flow Server.

    Proposed solution is to implement a direct integration feature between Flow Studio and GitHub, as an alternative to Flow version management. This feature would enable users to seamlessly push the XML files of their workflows directly to a GitHub repository from within Flow Studio.

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

11. Client Home Experience (Flow User Conference 2024)

    In Flow Connect users can access apps quickly through favorites section on the Home screen.

    In the future we would like to give users quick one click access to even more apps by opening up new possibilities to customize the client home screen.
    Users would be able to see a large number of apps and launch them directly from the home screen without navigating a folder structure.

    •  

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

12. Change Font, Colors, and Alignment within User Elements

    Within a User Element in a User Step, I would like to be able to change the font, front size, font color, alignment, bold, italics, and more so that I can make more visually appealing workflows.

    •  

    41 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

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

13. Push Notifications

    Flow Classic has a way to send push notifications via swimlanes. I have never been a fan of using swimlanes, but you could at least use them to send push notifications.

    In Flow Connect, I'd like to see Novacura implement a "connector" that could perform the same functionality. The connector could: iterate through a list of users, require a Push Notification message, optionally pass in an app GUID that would "forward" the user once they click on push notification to.

    Bonus points if you could use a websocket backend so this could also be implemented in the webclients as well and not just the mobile clients.

    Flow Classic has a way to send push notifications via swimlanes. I have never been a fan of using swimlanes, but you could at least use them to send push notifications.

    In Flow Connect, I'd like to see Novacura implement a "connector" that could perform the same functionality. The connector could: iterate through a list of users, require a Push Notification message, optionally pass in an app GUID that would "forward" the user once they click on push notification to.

    Bonus points if you could use a websocket backend so this could also be implemented in the webclients as well… 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  ·  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
    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.

14. Variable Types - Table

    Flow 6.15 and the earliest versions offer a possibility to choose a type of property which is either text or table. The latter ensures that more data can be stored under one property.
    Infor M3 Labs uses that funcitonality to store a dynamic data that affects the way how each and every workflow behaves, ie. the prompt proposals, buttons and input fields, automation of user steps are just a few to mention.
    In other words, the end-users, who more often than not are function-oriented, can utlize the table to adjust the values in the table.
    By that, workflows can be 'configured' according to one's wish and benefit, without necessarly editing the flow in the studio. On top of that, any alternative solution would require storing bigger amount of data outside of the Flow Server, which most likely would be extra charged.
    It would be great and of a big benefit if a similar function, that is a variable type - table, is available for Variables which will replace Properties.

    Flow 6.15 and the earliest versions offer a possibility to choose a type of property which is either text or table. The latter ensures that more data can be stored under one property.
    Infor M3 Labs uses that funcitonality to store a dynamic data that affects the way how each and every workflow behaves, ie. the prompt proposals, buttons and input fields, automation of user steps are just a few to mention.
    In other words, the end-users, who more often than not are function-oriented, can utlize the table to adjust the values in the table.
    By that, workflows can be… more

    •  

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

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

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

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

    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

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

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

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