4 results found

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

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

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

   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

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

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

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

4. Enforce Multi-Factor Authentication (MFA) for External Email Accounts

   Force Users to Enable Multi-Factor Authentication for External Email Providers

   Requested By:
   Customer Direktoratet for Samfunnssikkerhet og Beredskap

   Description:
   As requested by Customer DSB, the system should enforce Multi-Factor Authentication (MFA) for users who authenticate using external email providers such as Microsoft, Gmail, or other supported identity providers.

   This requirement is intended to enhance security and reduce the risk of unauthorized access caused by compromised passwords.

   Objective:
   Ensure that all users authenticate using two or more verification factors, improving account protection and aligning with modern security standards.

   Proposed Behavior:

   When a user logs in using an external provider (e.g., Microsoft, Google, or other supported identity providers), the system should verify whether MFA is enabled for the account.

   If MFA is not enabled:

   The user should be prompted to enable MFA before proceeding.

   Access to the application should be restricted until MFA is activated.

   The system should support common MFA methods, including:

   Authenticator applications (e.g., Microsoft Authenticator, Google Authenticator)

   Acceptance Criteria:

   Users signing in with Microsoft, Google, or other supported providers must have MFA enabled.

   If MFA is not enabled, the user is not allowed to access the system until MFA is configured.

   The system displays clear guidance for enabling MFA.

   MFA status is validated during authentication.

   Administrators may optionally enforce this policy globally.

   Benefits:

   Improved protection against account compromise.

   Reduced risk from phishing and password leaks.

   Compliance with customer security requirements.

   Stronger overall platform security.

   Force Users to Enable Multi-Factor Authentication for External Email Providers

   Requested By:
   Customer Direktoratet for Samfunnssikkerhet og Beredskap

   Description:
   As requested by Customer DSB, the system should enforce Multi-Factor Authentication (MFA) for users who authenticate using external email providers such as Microsoft, Gmail, or other supported identity providers.

   This requirement is intended to enhance security and reduce the risk of unauthorized access caused by compromised passwords.

   Objective:
   Ensure that all users authenticate using two or more verification factors, improving account protection and aligning with modern security standards.

   Proposed Behavior:

   When a user logs in using an external provider (e.g., Microsoft,… more

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