45 results found

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

   31 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

2. More user step controls (functional blocks)

   More UI controls/elements for endusers like progress bars, toggle, chip, filters, card layout, charts, map, tabs, timer, sliders,...

   •  

   19 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   15 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   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.

4. Enabling online/offline versatility

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

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

   9 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   planned  ·  AdminMalin Johansson (Admin, Novacura) responded

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

5. Ability to copy "Label Static Text" data from all clients

   In many cases user would like to use the data in Novacura Clients in other apps. Like to copy text from a work order and past into an e-mail. Or to fetch the work order number and query in another app.

   Today it works in Android client and of course the web client. It doesn't work in the iOS client.

   ==>Make all clients similar with same capabilities.

   •  

   •  

   9 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

6. Allow Client messages to display for Flowscript step

   Since Flowscript is so powerful now we can put extensive Scripts/loops in the script. If we do that in a userflow we cannot tell the user what's happening, because currently we have no way to add a client message like in other steps. Would be nice if we can get a flowscript function to add messages at different steps of the script execution. Otherwise UX for long running processes will be poor (missing user feedback)

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

7. Navigation workflow

   A clear and flexible way to move between user steps in navigation-based apps.
   Navigation items replace the fixed buttons at the bottom of the step and allow navigation to other steps in the app. An exit can carry data to the next user step, for example, passing the data of a selected item in a repeated control.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

8. Contextual Tooltips

   Implement a reusable tooltip component to provide on-demand context across all UI elements. This addresses the need for detailed explanations behind short labels, buttons and ensures small chart values are easily accessible.

   •  

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

9. Flexible layouts

   User steps need flexible layouts to support dynamic, section based designs to place buttons and controls exactly where you need them.

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

10. expand option in web client

    In the web client, when a grid is present in the user step, an option appears to expand the UI to the full browser window.

    Feature request: always show the expand option for the user's step (regardless of whether there is a grid inside).

    Also, make it a designer option to default to expanded or collapsed. Today it seems to remember my choice next time I run the app, but that is probably only for that app and that browser. Be able to control it more generally, both as an admin and as a user.

    •  

    •  

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

11. Direct Client-to-External System calls via OpenID Connect

    Enable connect Apps built on Novacura Flow Connect to communicate directly to external systems (e.g., IFS Cloud or other REST-based services) when the external system supports OpenID Connect (OIDC) for client authentication.
    This will allow secure, client-only communication, reducing dependency on the Flow Connect Cloud for certain REST API calls and improving performance by eliminating unnecessary round trips through the cloud.

    Business Value
    Performance: Reduce latency by avoiding cloud roundtrip.

    Scalability: Offload traffic from the Flow Connect cloud.

    Security: Leverage OpenID Connect’s standardized authentication and token handling.

    Scope
    Applicable only for Mobile & windows clients (assuming it will not work for web clients due to COARS issues)
    Supported only for external systems with OIDC and HTTPS endpoints

    Enable connect Apps built on Novacura Flow Connect to communicate directly to external systems (e.g., IFS Cloud or other REST-based services) when the external system supports OpenID Connect (OIDC) for client authentication.
    This will allow secure, client-only communication, reducing dependency on the Flow Connect Cloud for certain REST API calls and improving performance by eliminating unnecessary round trips through the cloud.

    Business Value
    Performance: Reduce latency by avoiding cloud roundtrip.

    Scalability: Offload traffic from the Flow Connect cloud.

    Security: Leverage OpenID Connect’s standardized authentication and token handling.

    Scope
    Applicable only for Mobile & windows clients (assuming it will not work… more

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    We are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.

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

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

13. Reintroduce "Multiline" Behavior for Text Input Boxes in NG Web Client

    The feature request aims to bring back the "Multiline" behavior for text input boxes in the NG web client, similar to how it worked in the old web client. This enhancement will allow users to expand text input boxes to accommodate multiple lines of text, providing a more seamless and user-friendly experience when dealing with longer inputs or when composing messages that require a larger writing space. By reintroducing the "Multiline" behavior, users can effortlessly resize text input boxes, leading to improved productivity and enhanced user satisfaction.

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  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. My Work - reduce cliks on errors

    The process of “skipping items” that contain errors in My Work is now 3 clicks, with no way around it.

    This used to be one click per “delete.” Ideally there are not a ton of errors, but if there are, it now means 3x the amount of clicking for the user (potentially on a small mobile device).

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

15. Hide/remove Assertion Step label from display in application runtime.

    We want to change how Assertion Steps are displayed to the user who runs the app. It is annoying and impractical that the label of the Assertion Step is shown to the user. Better to only show the phrase, as it worked in Classic. It is confusing and language-mixing for the user to see the label of the Assertion step. (See enclosed files).

    For me, this should be permanently changed or at least make it an option to hide the Designer label of the Assertion Step from the user who runs the app in the client. Our clients use assertion steps to say messages in the user language like "You may only select 1 item." or "Address field may not be empty" and when this is combined with the label from the Assertion Step in Designer the message looks confusing and improfessional, like there has been some error.

    We want to change how Assertion Steps are displayed to the user who runs the app. It is annoying and impractical that the label of the Assertion Step is shown to the user. Better to only show the phrase, as it worked in Classic. It is confusing and language-mixing for the user to see the label of the Assertion step. (See enclosed files).

    For me, this should be permanently changed or at least make it an option to hide the Designer label of the Assertion Step from the user who runs the app in the client. Our clients use assertion… more

    •  

    •  

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

16. The Network connection was lost error proper way of handling

    Now when you run some app on mobile device and you toggle off screen/switch app/small lack of internet, you will get The Network connection was lost message. It will take you back to previous step without proper indication and some of the machine steps will be already done. Would be good to have:
    -more explanation on help web page about such error messages
    -some kind of batch processing posibilites to handle such activity

    •  

    •  

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

17. Support multiple lines in inbox view

    As a user/technician, I want the inbox to support multiple lines so I can quickly check task details like priority, address, and phone number without opening each task, allowing me to select the right one efficiently.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

19. Remember enduser selected settings - Data grid

    Remember from before if end user chose card or table layout and open it the next time they log in. Can be extended to other user step elements.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

20. Clients - preview mobile and tablet layouts from Web

    Flow Developer would like to run the app in different screen sizes while developing to get a quick overview of how the application would look like for endusers

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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