290 results found

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

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

3. Data Grid Date

   Possibility to use date selector in Data grid element.
   Today only text, number, Lovs, checkboxes is valid for use. But many customers also ask for the possibility to use a Calendar for date fields to be possible to use.

   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

4. Contextual Copilot

   Contextual Copilot
   We are considering a simpler version of a contextual Copilot, aimed at enhancing user productivity by providing real-time, relevant assistance. This tool would:
   Help users complete tasks faster.
   Reduce errors and friction in workflows.
   Promote discovery of hidden features.
   Ultimately boost user satisfaction and adoption.

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

5. SmartDoc Insights

   AI-powered functionality designed to automate the classification and data extraction processes for uploaded documents. It simplifies workflows by identifying document types and extracting essential information, providing users with ready-to-use data while reducing manual effort and errors.
   Document Classification:
   Key Data Extraction:
   Benefits:
   Increases operational efficiency by automating repetitive tasks.
   Delivers accurate, actionable data with minimal manual intervention.
   Supports diverse applications

   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  ·  AI  ·  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  ·  Anonymous 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. AI Step

   Solution: Introduce an AI Step in the Designer that allows users to seamlessly integrate pre-defined AI tasks into their workflows. These tasks will enhance workflows with cognitive capabilities such as text analysis, image recognition, and predictive modeling.

   What It Does:
   Users can drag and drop an "AI Step" into a workflow.
   From a dropdown menu, they select from a set of AI tasks to execute within the workflow.
   Incremental Rollout: The library of AI tasks will grow incrementally, with new tasks added based on user demand and technological advancements, ensuring continuous improvement of capabilities.
   Examples of AI Tasks:
   Text Processing:
   Text summarization
   Sentiment analysis
   Named entity recognition (extract key information, like names, dates, locations)
   Document Automation:
   Document data extraction (e.g., extracting key data fields from invoices or contracts)
   Document classification (e.g., categorizing documents into types)
   Image Processing:
   OCR (Optical Character Recognition) for extracting text from images
   Image classification (e.g., identifying objects in images)
   Data Insights:
   Predictive analytics (e.g., forecasting sales or detecting anomalies)
   General Automation:
   Language translation
   Automatic task prioritization based on contextual inputs
   Smart recommendations (e.g., recommending next best steps)

   Solution: Introduce an AI Step in the Designer that allows users to seamlessly integrate pre-defined AI tasks into their workflows. These tasks will enhance workflows with cognitive capabilities such as text analysis, image recognition, and predictive modeling.

   What It Does:
   Users can drag and drop an "AI Step" into a workflow.
   From a dropdown menu, they select from a set of AI tasks to execute within the workflow.
   Incremental Rollout: The library of AI tasks will grow incrementally, with new tasks added based on user demand and technological advancements, ensuring continuous improvement of capabilities.
   Examples of AI Tasks:
   Text Processing:… 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  ·  AI  ·  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  ·  Anonymous 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. AI Flow builder

   Problem: Creating workflows manually can be time-consuming and error-prone, especially for complex business processes. Businesses need a faster, more accurate way to generate workflows that align with their domain and data models.
   Why It Matters: Manual workflow creation delays application development and increases the risk of misalignment with business objectives, leading to inefficiencies and higher costs.
   Proposed Feature/Idea
   Solution: Use AI to automatically generate workflows from user inputs, such as:
   A prompt described in plain language (e.g., "Create a workflow to move inventory parts").
   Existing business process or data model diagrams (e.g., BPMN, UML).
   What It Does: AI analyzes the input to:
   Understand the business logic.
   Create workflows (like the one in the attached image) that can be directly used as a domain and data model in the low-code platform.
   Example: Input a business prompt or upload a diagram, and the system generates a workflow like the "Move Inventory" process diagram in the attachment.
   Business Impact
   Time Savings: Reduces workflow creation time by up to 80%.
   Error Reduction: Ensures workflows are consistent and accurate based on predefined business rules and domain models.
   Scalability: Enables faster scaling of applications by automating repetitive workflow design tasks.
   Key Features/Capabilities
   Input Options:
   Plain-language text prompts.
   Uploaded business process or data model diagrams (e.g., JSON, XML).
   AI-Powered Generation:
   Natural language processing to interpret text.
   Diagram parsing to identify workflows and relationships.
   Workflow Outputs:
   Fully editable workflows in the low-code platform.
   Integration-ready domain and data models.
   User Feedback Integration:
   Allow users to edit and refine workflows with suggestions provided by AI.

   Problem: Creating workflows manually can be time-consuming and error-prone, especially for complex business processes. Businesses need a faster, more accurate way to generate workflows that align with their domain and data models.
   Why It Matters: Manual workflow creation delays application development and increases the risk of misalignment with business objectives, leading to inefficiencies and higher costs.
   Proposed Feature/Idea
   Solution: Use AI to automatically generate workflows from user inputs, such as:
   A prompt described in plain language (e.g., "Create a workflow to move inventory parts").
   Existing business process or data model diagrams (e.g., BPMN, UML).
   What It Does: AI analyzes the… 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

   3 comments  ·  AI  ·  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.

8. Pop up notifications support for seeded inbox

   When using seeded inboxes in App's we will have to go into the menue to see howmany requests are available. Ex: Approval APP, howmany records are there for user to approval.
   However it would be great to have a feature that gives notifications if they have any pending for requests shown externally (without having to click on the menu). Ex: like a pop up notifications etc.

   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

9. Mathematical Constants in Flow Script

   Introduce additional functions or constants in Flow Script that provide users with direct access to key mathematical constants such as "e" and "Pi".

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

10. Allow Scheduler Portlet to listen to "onRefresh" of other portlets, particularly the record viewer

    In some instances the drag-and-drop functionality of the Scheduler is not ideal, but you still want to display the data in a Scheduler and edit it in a separate portlet like the Record Viewer. This works, however the changes are not reflected in the Scheduler portlet until it is refreshed, and you cannot set a Scheduler portlet to listen to OnRefresh from a Record Viewer Portlet.

    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  ·  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. Update Web Service connector with new WSDL file once connector has already been setup on Cloud

    Currently a WSDL contract is necessary when creating the connector. However, once the connector is set up, it doesn't need ongoing access to the contract. On an on-premises server setup, the contract could simply be placed in the file system and accessed from there. However, on a cloud setup, direct file system hosting isn't possible.

    One suggestion is using a file system connector, which would allow users to upload the file onto the cloud server and then point to it. However, this approach is somewhat unconventional and a bit of a “rouge style”. An additional layer of complexity exists if there are linked XSD files in the WSDL. If the WSDL is to be hosted on disk, it needs to be self-contained, meaning all necessary components, like XSD files, should be integrated directly within the WSDL or be locally referenceable without external dependencies. Ultimately, the best option is that the contract need to be hosted as a proper web service or the WSDL must be modified to ensure it is self-contained if hosted from a disk.

    Currently a WSDL contract is necessary when creating the connector. However, once the connector is set up, it doesn't need ongoing access to the contract. On an on-premises server setup, the contract could simply be placed in the file system and accessed from there. However, on a cloud setup, direct file system hosting isn't possible.

    One suggestion is using a file system connector, which would allow users to upload the file onto the cloud server and then point to it. However, this approach is somewhat unconventional and a bit of a “rouge style”. An additional layer of complexity exists if… 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  ·  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

12. Option for Daylight Saving Adjustments in Addition to Static UTC for Scheduled Workflows

    As a user, I would like the option for scheduled workflows to adjust for daylight saving changes, as the system currently only supports a static UTC setting. Adding this flexibility would accommodate different timing needs, allowing for both local time adjustments and consistent UTC scheduling.

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

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

13. Improve Windows Tablet Compatibility for Web Forms web client – Bluetooth Integration, Photo Attachment, and UI Navigation

    Recent user feedback from field training highlighted critical challenges when using the Novacura Web Forms web client on Windows tablets due to the absence of a dedicated Windows application. These challenges include a lack of Bluetooth integration, a non-streamlined photo attachment process, and navigation difficulties within the UI. Current issues prevent full functionality for mobile users on Windows tablets, prompting us to recommend using only Android or Apple tablets until a solution is in place.
    Details:
    1. Bluetooth Integration:
    o Issue: The current Windows Web Forms web client does not support Bluetooth integration, a critical feature for seamless field operations on mobile devices.
    o Impact: Bluetooth functionality is central to several workflows, and without it, a significant portion of the app's functionality is unavailable, limiting the usability of Windows tablets.
    2. Photo Attachment Process:
    o Issue: Users must capture photos externally, save them, locate them in the file system, and manually attach them in the platform.
    o Impact: This multistep process hinders efficiency, especially in field conditions where speed and ease of use are essential.
    3. UI Navigation with Touch:
    o Issue: Navigating the Web Forms web client on Windows tablets without a mouse is challenging, particularly for scrolling within grids and selecting elements in confined spaces.
    o Impact: This creates a double-scroll issue (page scroll vs. grid scroll) that hampers usability with touch controls, especially when using gloves, a common requirement for field users.
    Suggested Solutions:
    • Bluetooth Integration: Develop or enable Bluetooth functionality within the Web Forms web client.
    • Photo Attachment: Streamline photo attachment, perhaps by enabling direct access to the camera for image capture within the app.
    • UI Optimization for Touch: Optimize the UI for touch interaction to reduce double-scroll issues, improve selection accuracy, and enhance usability without a mouse.

    Recent user feedback from field training highlighted critical challenges when using the Novacura Web Forms web client on Windows tablets due to the absence of a dedicated Windows application. These challenges include a lack of Bluetooth integration, a non-streamlined photo attachment process, and navigation difficulties within the UI. Current issues prevent full functionality for mobile users on Windows tablets, prompting us to recommend using only Android or Apple tablets until a solution is in place.
    Details:
    1. Bluetooth Integration:
    o Issue: The current Windows Web Forms web client does not support Bluetooth integration, a critical feature for seamless field operations… 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
    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.

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

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

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

16. New FlowScript function for BI apps and other data driven apps

    For data driven apps or any BI apps it would be great to have an easy way to create a complex result set of data.
    With this function available we could create amazingly flexible and "Qlik-like" apps in no time.

    Let's consider one scenario.
    We want to display sales per period, per a few selected sales reps and products.
    As dimensions we have Period (Quarter/Month), Salesman, Product.

    For the actual sales we have one big fact table with all all sales, including the dimensions above.

    In an app we want to select a group of salesmen and a few product, and then display, sales per quarter.

    For this we need two operations (possibly in one FlowScript function):
    1. Combine
    2. Populate

    Combine: Create one table with all combined dimensions (like an outer join without a on/where clause)

    Populate: Map one (or more) columns from the fact table and put the aggregated result in the corresponding cell in the combined dimension table. Have a default expression for the cells without any value. This table would the be the output from the function.

    The output could then be used to display & update data in a effective and comprehensive way.
    Of course this can be done using existing FlowScript functions, but the suggested function would save a lot of time and have the potential to create a lot more flexible solutions.

    For data driven apps or any BI apps it would be great to have an easy way to create a complex result set of data.
    With this function available we could create amazingly flexible and "Qlik-like" apps in no time.

    Let's consider one scenario.
    We want to display sales per period, per a few selected sales reps and products.
    As dimensions we have Period (Quarter/Month), Salesman, Product.

    For the actual sales we have one big fact table with all all sales, including the dimensions above.

    In an app we want to select a group of salesmen and a few product,… 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  ·  Designer  ·  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

17. As a user, I want the Batender connector to support the 64-bit version of BarTender, as it currently only works with the 32-bit version of

    As a user, I would like the Bartender connector to add functionality for the 64-bit version of BarTender, as it currently only supports the 32-bit version of BarTender 2016 R8 (Automation or Enterprise Automation Edition).

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

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. Portal Scheduler: allow buffering of changes / What If Mode

    In the current Portal 2, drag&drop option, resizing or moving of tasks get synchronized and data set is loaded again.

    It would be great, if we have options here. Eg. the changes are not synchronized and only shown right away.
    Datasets can be big and load for 1 - 5 seconds, if a lot of resizing happens, this is noticeable to the enduser. I could see more than one solution:
    - add option to synchronize changes instantly (todays functionality)
    - add option to trigger all changes
    - synchronize the changes in the background (similar to offline functionality). This would only visually show the changes in the front end and not reload the data set, but working on the changes in the background.

    In the current Portal 2, drag&drop option, resizing or moving of tasks get synchronized and data set is loaded again.

    It would be great, if we have options here. Eg. the changes are not synchronized and only shown right away.
    Datasets can be big and load for 1 - 5 seconds, if a lot of resizing happens, this is noticeable to the enduser. I could see more than one solution:
    - add option to synchronize changes instantly (todays functionality)
    - add option to trigger all changes
    - synchronize the changes in the background (similar to offline functionality). This would only… 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  ·  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

20. Add "Sortable" Option to Table Portlet in Portal 2

    Portal 2 currently lacks the option to disable the sortable functionality in table portlets, a feature that was available in Portal 1. This feature is crucial, especially for touch device users, as the default sortable setting can lead to accidental data reorganization or confusion when interacting with the interface.

    Proposed solution is to reintroduce the "Sortable" option in the table portlet settings within Portal 2. This feature should allow administrators to toggle sorting capabilities on and off according to the specific needs of their interface design or user experience requirements.

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