117 results found

1. AD Sync (SCIM) for Flow Connect

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

   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

   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

   Submit Rating

2. SFTP/FTP Connector

   To be able to communicate with SFTP/FTP systems in Flow Connect

   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

   0 comments  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Offline Data in Flow Connect

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

   9 votes

   Vote Vote Vote

   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

   Submit Rating

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

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

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

   •  

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   planned  ·  AdminIrshad Hassan (Admin, Novacura) responded

   The feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.

5. File System Connector

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

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

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

   20 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

   Submit Rating
   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

   •  

   37 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  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Submit Rating
   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. Map Portlet in Connect

   The Map Portlet is already a valuable tool for customers using Portal 2, allowing them to visualize spatial data and navigate easily within a mapped environment. To ensure a seamless transition to Portal Connect, we are bringing this functionality forward—along with some exciting enhancements.

   The Map Portlet in Novacura Flow Portal Connect will not only retain the core features from Portal 2 but also introduce new capabilities, including:

   Interactive Map: Users can zoom, pan, and navigate smoothly to explore spatial data.
   Real-Time Markers: Display live positions of equipment, personnel, or other points of interest.
   App & Component Integration: Click on markers to trigger apps or interact with components for faster workflows.
   Customizable Layers: Add multiple layers to visualize different types of information on the map.

   These improvements will empower users to better analyze and interact with spatial data, enabling more informed decisions and enhancing operational efficiency.

   The Map Portlet is already a valuable tool for customers using Portal 2, allowing them to visualize spatial data and navigate easily within a mapped environment. To ensure a seamless transition to Portal Connect, we are bringing this functionality forward—along with some exciting enhancements.

   The Map Portlet in Novacura Flow Portal Connect will not only retain the core features from Portal 2 but also introduce new capabilities, including:

   Interactive Map: Users can zoom, pan, and navigate smoothly to explore spatial data.
   Real-Time Markers: Display live positions of equipment, personnel, or other points of interest.
   App & Component Integration: Click on… 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

   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

   Submit Rating
   planned  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   The feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.

10. Chatbot Assistance in Custom Content Portlet

    Use a chatbot to help build the CSS and HTML in the portlet.​

    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

    Submit Rating

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

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

12. Swimlanes

    Swimlanes in Flow Connect, much like Classic, would support multiple roles and push notifications to role. Currently, Swimlanes on Connect are converted to Seeded Inboxes.

    Swimlane functionality on Classic can be found here:
    https://help.novacuraflow.com/development/flow-studio/applications/workflow/swimlanes

    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

    Submit Rating

13. As a user, I would like to open a Flow app on mobile directly from a QR code.

    As a user, I would like to open a Flow app on mobile directly from a QR code.

    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  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add Query Parameters to External URLs in Link Portlet

    Pass dynamic data through links. For example, add a link to be able to navigate to specific work order in IFS.

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

    Submit Rating

15. Container in Container

    Customers have consistently asked for more flexibility when designing their portals. While Connect has already expanded the design area from 12 to 24 columns, there’s still a need for more advanced layout options to meet growing demands.

    For example, many partners have requested the ability to place multiple portlets (such as a filter and a table) within a single tab using a stacked container. This and similar use cases highlight the need for a more adaptable and intuitive layout system.

    What’s Coming:
    We’re introducing new features that will give users more control over portal layouts, including:

    Expanded Design Options: Greater flexibility for customizing layouts and branding.
    New UI Structures: Support for different container types, including:
    • Horizontal layouts
    • Vertical stacks
    • Stacked containers (e.g., filter + table)
    • Repeating sections for dynamic content

    Data-Driven Containers: Containers can act as a data source, allowing child elements to inherit and display relevant data.
    Custom Buttons in Containers: Add action buttons directly within containers for smoother user interactions.

    These enhancements will empower users to create richer, more tailored portal experiences, ensuring that the portal adapts to their business needs—rather than the other way around.

    Customers have consistently asked for more flexibility when designing their portals. While Connect has already expanded the design area from 12 to 24 columns, there’s still a need for more advanced layout options to meet growing demands.

    For example, many partners have requested the ability to place multiple portlets (such as a filter and a table) within a single tab using a stacked container. This and similar use cases highlight the need for a more adaptable and intuitive layout system.

    What’s Coming:
    We’re introducing new features that will give users more control over portal layouts, including:

    Expanded Design Options: Greater… 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

    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

    Submit Rating

16. Option to search in translations tab

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

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    planned  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

    The feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.

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

    Submit Rating

18. Conditional color rules in Table Portlet in Portal 2

    It would be great if it was possible to set the cell color for column 'x' depending on the value in column 'y'. Today in classic, we add x-number of invisible HTML-symbols in the data source for column 'x', render the table portlet as "HTML" and then set the color rule of many invisible symbols the column 'x' has.

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

    Submit Rating

19. Image Annotation to Provide IsEdited True/False

    Currently, the image annotation has no way of determining if an image is edited or not. This means, that each time an image is either edited or not, I need to re-save it to the database. This is a performance issue since at times, I can present 20 images in a File Gallery and have no way of determining which ones I should save and which ones I should not save to the database.

    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

    Submit Rating
    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. Feature to log REST calls

    It would be nice if we could log somehow if an enduser run a workflow and during a REST call an error occurs, then later a developer could check these log files. Or if the issue is not reproducable in DEV environment, only in PROD/TEST env. (like a similar functionality in Flow Classic).

    A use-case from partner:
    "If the user experience problems occasionally and we can’t recreate it in the debug.
    Another example, sometimes when I get long responetimes during testing I cannot see if that is because of M3 or not. Next time I run it it is quick again."

    It would be nice if we could log somehow if an enduser run a workflow and during a REST call an error occurs, then later a developer could check these log files. Or if the issue is not reproducable in DEV environment, only in PROD/TEST env. (like a similar functionality in Flow Classic).

    A use-case from partner:
    "If the user experience problems occasionally and we can’t recreate it in the debug.
    Another example, sometimes when I get long responetimes during testing I cannot see if that is because of M3 or not. Next time I run it it is quick… 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  ·  Connectors  ·  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

    Submit Rating