86 results found

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

   •  

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

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

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

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

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

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

6. Manual re-compile all enabled projections in OData connector

   In the context we hae customers like Elvia and soon DSB where flow is having a usage of 300+ projections. With frequent updates in IFS ( ever green with new releases every 6 month and service updates in addition). The projections needs to be recompiled one by one. This is timeconsuming and have a risk of not handling it correctly.

   I would be great and useful to add an option/button/way to easily re-download the metadata of all enabled projections and re-compile them in OData connector.

   Especially, after an update of IFS, it would be great to do it manually.

   Even if just the admin page gets this function(like: https://odata-ifscloud.novacuradev.net/) and not from machine steps in flow studio.

   In the context we hae customers like Elvia and soon DSB where flow is having a usage of 300+ projections. With frequent updates in IFS ( ever green with new releases every 6 month and service updates in addition). The projections needs to be recompiled one by one. This is timeconsuming and have a risk of not handling it correctly.

   I would be great and useful to add an option/button/way to easily re-download the metadata of all enabled projections and re-compile them in OData connector.

   Especially, after an update of IFS, it would be great to do it manually.

   Even… more

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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.

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

   •  

   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

   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.

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

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

10. On-Premise (onprem) Runtime

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

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

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

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

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

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

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

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

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

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

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

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

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    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

    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

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

    •  

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

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

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

15. Datepicker in Filter Portlet Start Date by User's Locale

    The starting day of the week in a datepicker in Portal 2 should be influenced by the locale settings. For instance, if en-US, the week start should be Sunday. If sv-SE local is set on the Flow User, then Monday should be the start date.

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

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

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

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

18. Enhanced Flow Variable Update Capability Within Scripts

    A feature enhancement that allows users to update the values of flow variables from outside of a script. Currently, when working with variables X and Y, executing a script step only allows for returning a value to overwrite one of them, or utilizing a complex workaround with a record to update both variables. We propose the addition of a simple syntax, such as ":flow.X = "something";" within the script, where the ":flow" prefix defines the scope of the variable being modified. This improvement will streamline the process of updating variables, eliminating the need for additional steps and making script operations more efficient and concise.

    A feature enhancement that allows users to update the values of flow variables from outside of a script. Currently, when working with variables X and Y, executing a script step only allows for returning a value to overwrite one of them, or utilizing a complex workaround with a record to update both variables. We propose the addition of a simple syntax, such as ":flow.X = "something";" within the script, where the ":flow" prefix defines the scope of the variable being modified. This improvement will streamline the process of updating variables, eliminating the need for additional steps and making script operations… 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

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

20. Provide information to Hub users on app versions that are deployed to environments other than DEV.

    Use case: we use TEST environment to maintain stable apps that are share-worthy with customers. And use DEV to continue our developments, enhancements, testing etc.

    Problem: No share option for applications that are deployed to TEST.

    Idea: Provide information to Hub users on app versions that are deployed to environments other than DEV, so that users can generate share links to match deployed app versions more efficiently.

    •  

    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

    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
    started  ·  AdminAndreas Berggren (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.