Skip to content

Settings and activity

2 results found

  1. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Mohamed Ifham supported this idea  · 
  2. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Mohamed Ifham supported this idea  · 
    An error occurred while saving the comment
    Mohamed Ifham commented  · 

    I would be happy to go with option 1, incorporating both options 1.a and 1.b, as if they can be mutually inclusive.

    1. This approach allows for easy modifications and adjustments to report design without requiring extensive technical intervention, making the tool accessible to a broader audience, which aligns with our business motto.
    2. Intuitive drag-and-drop interfaces might allow for quick and easy report creation and minimizes errors that can occur when manually coding HTML for report design.
    3. Ensures consistency across reports by using standardized templates and design elements.
    4. Reduces the need to transmit sensitive data to the server for PDF generation, enhancing data privacy and security
    5. Provides users with more control over the PDF generation process, including customization and immediate preview capabilities.
    6. Reduces dependency on network connectivity and backend services, enhancing reliability in environments with unstable internet connections.

    Option two has many drawbacks, as mentioned in the post. It would be better to introduce a new feature in Flow Connect that differentiates it from the classic version and provides a higher competitive advantage.

    I reviewed the option 3 convert API privacy terms, and it's clear they do not take responsibility for data breaches during data transfer. Users must assume full responsibility for data breaches. Since we already have this functionality in Flow Classic, it would be disappointing to choose this option, as it would diminish Flow Connect's capabilities. Additionally, the pricing terms could negatively impact our customers using Flow Classic, as they might have to pay extra for this functionality, leading to potential dissatisfaction with Flow Connect.