290 results found

1. Flow connector / Studio Reports in Flow Connect

   In classic customers are using the Flow Connector, or reports from the Studio, to extract meta data about the system such as:
   Last Logged in,
   Number of logins

   A similar report in Connect is needed

   •  

   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  ·  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. Allow custom text for invitation mails to Connect

   Customer employees frequently ignore Connect invitations as Spam. It would be good if the customer can write their own custom invitaiton messages.

   1 vote

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

3. Default Landing Page when the user logged in - Portal

   Current Behavior
   On first-time login, the contractor portal is expected to default to the Dashboard (as per system design).

   However, users have observed that it sometimes lands on the Technician tab instead.

   For subsequent logins, the portal loads the last visited tab, as this preference is stored in the browser cache.

   Technical Clarification
   The system currently:

   Defaults to the first available page (Dashboard) only when no cached session data exists (e.g., incognito mode or cleared cache).

   Stores the user’s last visited page in browser cache, which determines the landing page on future logins.

   This behavior cannot currently be overridden without:

   Clearing cache, or

   Using a direct URL with a predefined page selection.

   Gap / Clarification Required
   There is no formally defined requirement confirming:

   Whether the landing page should always default to a specific tab (e.g., Dashboard), regardless of cache.

   Need confirmation if:

   Defaulting to the Technician tab in some scenarios is expected, or

   The system should always enforce Dashboard as the landing page.

   Requested Changes
   Default Landing Page: Dashboard (for every login, not only first-time use).

   Dashboard Default Filter: Last 30 days.

   Request
   Explore feasibility with R&D to:

   Override browser cache behavior and enforce Dashboard as the standard landing page without requiring a custom URL.

   Confirm level of effort compared to legacy CE portal behavior, where this was supported.

   Current Behavior
   On first-time login, the contractor portal is expected to default to the Dashboard (as per system design).

   However, users have observed that it sometimes lands on the Technician tab instead.

   For subsequent logins, the portal loads the last visited tab, as this preference is stored in the browser cache.

   Technical Clarification
   The system currently:

   Defaults to the first available page (Dashboard) only when no cached session data exists (e.g., incognito mode or cleared cache).

   Stores the user’s last visited page in browser cache, which determines the landing page on future logins.

   This behavior cannot currently be overridden without:

   … more

   1 vote

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

4. Remove Option for SCIM managed users from Flow connect

   Currently there is no way to remove the SCIM managed users from Flow connect.
   I can only either revoke the token or regenerate it but it will break the entire SCIM provisioning done for all the organization.the best approach is to ask the customers to remove the required user groups from the SCIM app registration in Entra ID. However, we should also have our own control over this, specially if the configuration was originally done for a PoC and when the PoC ends, there should be a mechanism to ensure that access is also disabled from our side.

   1 vote

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

5. User Context Switching for Kiosk mode apps

   We see more and more requirements from customers wanting to run Novacura Flow Connect in kiosk mode, where several users would use the same computer to basically run the same apps (e.g. for Inventory Operations or Shop Floor reporting).

   For this reason it would be super useful to be able to easily and quickly switch user context from the client.

   This would require two things:

   1. Having the practical option to switch user. Maybe even including a simplified login process using for example a pin code

   2. Being able to also switch back end user context. For IFS10 we can use Run As. For IFS Cloud there's no similar possibility. However, we have the ROPC authentication option. Would it be possible to have the ROPC User as a variable?

   Having this type of user context switching would also avoid license sharing, meaning would be able to keep license count equal to physical user count.

   We see more and more requirements from customers wanting to run Novacura Flow Connect in kiosk mode, where several users would use the same computer to basically run the same apps (e.g. for Inventory Operations or Shop Floor reporting).

   For this reason it would be super useful to be able to easily and quickly switch user context from the client.

   This would require two things:

   1. Having the practical option to switch user. Maybe even including a simplified login process using for example a pin code

   2. Being able to also switch back end user context. For IFS10 we can use Run… more

   1 vote

   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

6. Highlight hidden columns in calendar control

   Tiny request for those configuring calendar in user step: In the Edit columns section could it be possible to highlight columns that are hidden?

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Designer  ·  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. Component Step in workflows

   Possibility to modify an already added component step in a work flow. Currently after we add a component as a step in a workflow, there is no possibility for us to modify that step. We have to create a new step and map the component from scratch. In flow classic, it was possible for us to change the existing step. This additional work is hectic. please allow developer to change the Component step within a flow when by modifying the current step. Also make component workflows available for every application instead of the application it is developed in.

   •  

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

8. View Code in Designer

   In Flow Connect, it would be nice to view the code of the workflow to make changes in bulk. This was possible in Flow Classic.

   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

   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

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

10. Support for deciding which clients (portal vs. clients) an end-user can log in to

    Having a way to stop users or groups of users from being in the web client could be nice. The problem we are having is when users are completing registration they are getting driven to apps, but right now we are onboarding a lot of "portal only" users. So they get confused. We are sending a welcome email to link them to the board, but sometimes people don't read the email. When everything is said and done we have people who are web client only, portal only, and some who need both.

    1 vote

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

11. Option to default style of the GRID control (table/card)

    Hi,

    This Requests comes from the customer HomeServe.

    • Ability to default the Grid in Mobile clients to Card view.

    The Grid is very useful in the web client, it's harder to make it look good in the Mobile Clients where more than 2-3 columns often get cramped by the smaller screen size of the devices and the user needs to scroll sideways. And sometimes the Card layout of the Grid is just a better option to display data.

    •  

    •  

    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

12. Allow Barcode scanner feature on/off for input fields

    Some customers don't want the option to use barcode scanning (camera) on some input fields and want it on others (to prevent data errors)
    We should have an option to enable / disable this.

    •  

    1 vote

    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

13. Allow to run Components with user steps in the portal

    Since there is no function in the portal today to determine whether user steps are present in components, all components start silently. And at runtime, if the component has a user step, an error saying: "Invalid usage of user step within component" is displayed.

    Such a function would allow components with and without user steps, increasing the usability

    1 vote

    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

14. Liquid & XLST Transformers for automations

    All ow automations to perform transformations on input and output for webhook triggers so we can support current classic customers in connect

    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

    2 comments  ·  Integration  ·  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  ·  AdminAlbin Lundberg (Product Owner, 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.

15. OFFLINE ALERTS

    For OFFLINE Mode, give the user an alert when the capacity defined on devices are closed to be reached to request a synchronisation. Provide on Admin Portal the remainign capacity on devices connected to OFFLINE to manage synchronisation.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

17. Push refresh of portlet

    Have an option from an app/component to send a refresh command to a portlet for a specific user.

    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  ·  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
    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. Preview of pdfs and images in file gallery in the Clients

    When our users are out using their phones (iOS and Android) and having quite a few files displayed in the file gallery, they would like to see small thumbnails of the content of the file (like can be seen in windows).
    Or, use some tag or in another way associate the file with specific function.

    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

19. 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
    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. Navigation in a page tree

    When using empty pages as navigation parents in the portal, users report confusion when clicking them, since they only see a blank page.

    Options to perhaps set a default child page if the parent is empty, or Git Book style, clearly show the child pages on that empty parent page

    •  

    1 vote

    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