OutSystems and Ultimate PDF

Introduction:

Developers can use Ultimate PDF to create PDF documents dynamically by fusing customizable templates with data from their OutSystems application. This makes it possible to create reports, invoices, and other PDF-based documents.

In our OutSystems, we have access to download more plugins from forge. But, in this case, I ‘am using one particular component that is called ultimate pdf. This allows us to generate a pdf by giving the URL of the screen.

Its primary features are :

• Easy PDF Generation. This part makes the process of creating PDF files easier.
• Adaptable Templates. Developers can create and alter PDF templates to meet their own needs.
• Permit dynamic material (data) to be included in the PDFs that are produced.

If you want end users to be able to extract information from applications generating a pdf file is a good option. It has an entity called Resume it has some attributes. Drag and drop the entity here at the main flow editor and built the details screen.

How to use it?

Basically, you have to download and install the plugin from Forge directly from the application. You may find it under your application's manage dependencies section, where it will then display actions for you to take. This will accept the URL of the page you wish to export in PDF format, and return the PDF file. In order to create a PDF from the URL, we will no

Let's add a button to the screen that users can click to access a PDF file. When they do so, you can supply the logic to call the function in this case, Print by first searching for the file and then the URL of the page. Then, in the URL, we want to pass the URL of the current page. If you explore the built-in functions, you'll see that there are a few built-in functions for interacting with URL. This Get BookmarkableURL option is the one that provides us with the URL of the current page.

In this case, if we call it, it will run the current page's URL. After that, we'll replace this end with the download function here, enabling us to generate a file. Here, in the content, we'll get the output from the function above, and we can give it a name—for example, "Report.PDF"—that is either dynamic or just hardcoded. Once the extension is PDF, we can publish it.

So this is my page it has the list shows Resumes and the print function will triggered if I clicking on PDF Button, I will get the file.

There is now another possible variant of this. For instance: If a user clicks the "PDF" button on the PDF, it will export all of the specific resume, not just that specific resume. In that case, I would add a new column and put an icon (for PDF). When a user clicks it, I could bind it to a logic and create a new client action. This time, we would call the same function print and the URL, but instead of providing the URL of the screen that is currently displayed, we would like to provide the URL of the Resume detail.

You must now return to your page, copy the URL of one of the resumes, and follow my reasoning in trying to make the URL dynamic. So that, I can pass the ID in this case, the resume ID that is currently available in this query. Every time it becomes dynamic for each record variable when we are clicking that icon. Thus, clicking the icon will start the logic, which will then call the logic to create the PDF by using the ID of the current record in the list.

After that, we need to give the download link. The material will be from the PDF, and we should make the file name dynamic by adding the resume name. You may create any specific screen and convert it to a PDF before publishing it. You can even create a beautiful report. Only that specific record or that specific resume will be generated if we click on any of these.

We can also Download Multiple Resume in One PDF:

Created another screen called Resume Detail Multiple and in that screen list is created, then the source of the list will be from resume aggregate. That URL will be passed in the logic called (PrintToPDF).