Maybe you can use Printables and then build a server-side code that will convert the printable word to PDF, you can store the result in an activity for self keeping or etc.
You can use 3rd party DLL to convert the word to PDF.
As of now, the PDF conversion functionality is not available in the ootb version of the system.
Currently, we can recommend using the PDF conversion feature in MS Word by using the "Save As" option.
As a workaround, if it is necessary to prevent users from making changes to the PDF file after exporting:
You can upload a Word file with a password for modifications as a template for the printable. This way, the necessary data will be included in the file, but it will not be possible to make changes without knowing the password.
Additionally, we can suggest an alternative approach:
For what it's worth, I use Power Automate a lot to handle these kind of functions where Creatio lacks the functionality. You can handle the API response of Power Automate REST Trigger to give you the data back, etc...
If you are using 365 in your tech stack it, it could be an option.
It depends on where exactly you need to read this data. If you need to read it from external API call then you need to use then for example you can use the following link and perform GET request to it:
CreatioApplicationName should be replaced with your application name;
149d2eaf-cbd2-49fa-b565-637748ff823c should be replaced with the UId of the object where the file is stored (for accounts it's AccountFile and UId for it is 149d2eaf-cbd2-49fa-b565-637748ff823c):
c628b09b-05db-4ce5-968b-d38f5833978b should be replaced with an actual Id of the record inside AccountFile table (in your case - the object where the file is stored).
As a result you will get the file content:
If you need to do it in the business process then you need to take a look at the "Process file" process element which allows working with files. Or you can take a look at the file API that allows files processing though the server logic inside Creatio app.
as we use non-standard font for our report, it should be embedded into result pdf-file. FastReport has this option during export to PDF. But how can we achieve the same from Creatio?
There are several possible reasons why a custom font added to IIS for Fast Reports may work for one site but not for another, even with the same settings. Here are a few possible reasons:
Different versions of IIS: If the two sites you are configuring the custom font for are running on different versions of IIS, this can cause compatibility issues. Therefore, depending on which version of IIS your sites are running on, you should use the corresponding version of the custom font.
Different IIS settings: Another possible issue is different IIS settings on different sites. For example, if one site is working with custom fonts over HTTP, and another is over HTTPS, this can affect how the fonts are displayed on the site.
Different font locations: It's possible that the fonts are not located in the same place on two different servers, and this can cause issues with loading the fonts on one of the sites.
Caching: If the font is added to one site, and then you add it to another, the browser may have a cached copy of the old version of the font. This can cause the font to not change when you switch to the other site.
If this is a self-hosted font, it may be necessary to modify the hosting settings of the font to allow access from other domains (perhaps by adding the instance address of Creatio to the Allowed domains list).
To address these issues, make sure you are using the correct version of the font, check if the settings are the same on both servers, make sure the fonts are located in the same place, and clear the browser cache.
I need to do a custom button implementation, which will download the grid from the detail with all the data that is in the grid, like the similar function of the "PRINT" button.
Please feel to explore the printables in the below thread.
It is explained for Portal users and in the same way, functionality has to be implemented in your custom section (Please be informed to debug the modules explained in the article and use it accordingly for your functionality).
As far as I have explored Aspose.PDF Addon ,we are not able to create Pdf in studio can you provide some steps how to configure this addon in my Application in Sales.
Unfortunately, there is no such functionality for now.
We have already registered the idea for our R&D team to implement this functionality in further releases. I will assign your case to this project in order to increase its priority.
I've this situation where I need to add a new tab "Preview" and the main objective is have a iframe with a preview of the documents in the attachments, however we try first implement the logic if was a website, because we think that the article that we found on academy "https://academy.creatio.com/documents/technic-sdk/7-13/integration-third-party-sites-iframe"partially satisfies what we want to implement;
First, based on the Web field, we were able to do the preview of the website, as you can see on the image below.
Then, we try to call and access to the storage of the pdf that we have on the attachments (image below), but the only link that we have of the pdf is the link/method to download the file, for example: https://..../0/rest/FileService/GetFile/Id.
In this way we want to know if there is any way to acess a link or storage of the file, with objective to implement something like preview of the document with the iframe on the edit page.
I have added Aspose.PDF plugin to convert the Word to PDF printables. I have generated the 'Client ID' and 'Client Secret' as suggested in the guide.
Where do I key in these Client ID and Client Secret in System Settings? I am getting this notification - 'Please fill in the system settings for converting files to PDF'
Log in to Creatio, go to 'System Designer' → 'System settings' section, find and fill out the respective system settings. Log out and log back in to apply the changes.
'Save Printable' (keep in mind that we tried with a script first but we switched to this for ease of use)
Whenever we trigger our business process manually, the pdf gets created automatically. Whenever the BP gets triggered by the portal, the attachment doesn't get converted. We still use the same BP with the same values.
We call the invoice through API and set it to "Complete". As soon as this happens, we trigger the following flow which is the subprocess: https://prnt.sc/zz2uut
Here we have the "save printable" block.
Everything works except when the status is set to complete through the portal API.
Regarding the second issue, we need you to run a check-up and get back to us with the results.
Please set the printables generation to .docx printables in the subprocess in the 'Save printable' element. Run the business process and tell us if a .docx printable is successfully generated when the BP is triggered by the portal.
If we set the processs to docx, everything works. Right now, when we change the generated pdf (through portal) file to ".docx", we can open it in word.
Did you read the Installation > Guides and manualsRead Manuals on the marketplace page?
1. Register at Aspose.PDF service (https://products.aspose.cloud/pdf/net), add an application (My Apps> Add an App), get access keys (Client Secret, Client ID).
2. Fill in the system settings "Aspose API Access Key" (= Client Secret) and "Aspose Security Identifier (App SID)" (= Client ID) with the data from item 1, respectively. Logout and login to the Creatio app again.
3. Go to System Designer > Lookups > the ‘Printables’ lookup, select the printable, and open the printable setup page, select the ‘Convert to PDF’ checkbox and save changes. Note that the ‘Convert to PDF’ checkbox is available only on the printable setup page in the new UI.
4. The add-on shows an error message if a printable conversion fails on the Aspose side (Aspose service is unavailable, service access is not paid, etc.). Detailed error description is available in the browser console.
You can find an example of the Aspose API library call from Creatio in the 'AsposeCloud' package. Additional information on Aspose API SDK is available here - https://products.aspose.cloud/pdf/net.
The responsible team checked that the Aspose connector uses Aspose.Words.Cloud.Sdk.dll, which does not include the method that you need. You can find the description of the .Pages.Add() method that you need here: https://docs.aspose.com/pdf/net/merge-pdf-documents. Please install the required library and follow the Aspose official guidelines.
We have asked the team about possible development assistance, unfortunately, they cannot assist.
