Skip to content
← Novacura Flow Connect

How can we improve Novacura Flow Connect?

Novacura Flow Connect: Connectors

Categories

(thinking…)

HTML to PDF Connector

HTML to PDF connector is a frequently used connector for designing and generating PDF reports in Flow Classic. Additionally, it's also possible to merge existing pdfs with this connector.
As mentioned in this idea https://ideas.novacura.com/forums/956630-novacura-flow-connect/suggestions/48235034-add-proper-report-print-layout-configuration-to-fl
The design capabilities of the existing connector are somewhat limited/rigid. Ideally, it should be far easier/flexible to design a report layout in connect. Here are some options we can consider for HTML to PDF connector in Flow Connect.

Option 1

Can be divided in to two sub sections.
a. Report design as its own step in the designer – The idea of this is to have a new “report designer step” that is a low-code/WYSIWYG editor. With this approach, the flow developers do not design the report with HTML rather use the editor to design. So even someone who does not know HTML can design a report.

Advantage – Flexible, feature rich design capabilities with no HTML knowledge needed.

Disadvantage – Migrating existing customer flows with HTML to PDF connector in Flow Classic to this new format might be challenging.

b. Generate PDF report as a client feature – Once we have figured out a way to design the report, the PDF generation can happen in the client-side. This would enable offline PDF generation since we do not need to communicate with the Flow Connect backend for PDF generation.

Advantage – Offline PDF Generation. No connector setup is needed to design & generate reports.

Disadvantage – If the PDF’s are too big (in size) it will affect the performance of the client. especially in mobile/handheld devices with limited memory capacity. Might have an effect on battery life as well.

Option 1.a & 1.b are mutually exclusive. We can stop with option 1.a where a new design step that keeps the PDF generation server-side. Or we can have the existing report design machine step but have option 1.b to generate the PDF on the client side.

Option 2

Keep HTML to PDF connector as it is – We can also have the exact same functionality of the HTML to PDF connector in connect. So, a connector configuration is needed design & generate PDF reports as PDF generation is happening server-side. With this approach we can borrow lot of stuff from Flow classic (e.g. the design of the machine step) and reuse the existing connector infrastructure.

Advantage – Migration from Flow Classic to Connect will be easier. Also, since its server-side pdf generation, the connector should be able to handle relatively bigger PDF files.

Disadvantage – We will continue to have the same issues as it was in Flow Classic. (e.g. Rigid/lack of design capabilities, formatting & logos, no offline printing, etc..)

Option 3

Use a third-party service like ConvertAPI. Convert API also provides dedicated servers if needed.

Advantage – Already available and easy to setup with the existing REST Connector.
Access to other documents formats like DOCX,XLS,XLSX, TXT,JPEG.
Relatively easy migration from Flow Classic.

Disadvantage – Since its REST service hosted by a third-party 3rd party privacy terms apply.
Lack of on-Prem hosting options (e.g. Convert API does not provide any onprem hosting solution)

8 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

AdminIrshad Hassan (Admin, Novacura) shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Abdul Aloukla commented  ·   ·  Report

    I have addressed all the comments in the new PDF file and introduced two new options. My preference is to proceed with option 5, and should we choose this, we must ensure that all the requirements are fully implemented.

  • Mohamed Ifham commented  ·   ·  Report

    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.