Hi Satyam,

Yes, this can be achieved, but you need to handle both actions in one custom flow.

The recommended approach would be:

1. Generate the printable report using a business process or custom backend service.
2. Save/attach the generated report to the record’s attachment object, for example ContactFile, AccountFile, or the relevant {Object}File schema.
3. After the file is created and you have the generated file record Id, trigger the browser download using FileService/Download/{EntityFileSchemaName}/{fileId}.

For uploading/attaching a file manually, Creatio provides POST /FileApiService/UploadFile, where you need to pass parameters such as entitySchemaName, parentColumnName, and parentColumnValue.

So the key point is: do not only call the download service directly. First generate/save the report as a file attachment, then use the generated file Id to download it for the user.

If this needs to happen from a Freedom UI button, the button can call a custom service or process, wait for the generated attachment file Id, and then open the download URL in the browser.

smit suthar,

Hi,

Thank you for the detailed explanation.

I understand the overall approach, but I'm still a bit unclear on some of the implementation details in Creatio.

Would it be possible for you to elaborate on the following points:

1. In the case of a Freedom UI button, what would be the recommended way to wait for the file creation and then trigger the download automatically?
2. If possible, could you provide a simple end-to-end example (Business Process or Freedom UI implementation) demonstrating the complete flow?

A more detailed example would help me understand how these pieces fit together in practice.

Thank you for your help.

Hello,

Yes, Creatio supports this scenario out of the box through the Portal functionality and the built-in portal user self-registration mechanism.

A public user can access the portal registration page and create an account independently without administrator involvement. After completing the registration process, the user receives access credentials and can authenticate as a portal user. Once logged in, the user can work with the records, applications, requests, and other portal functionality that has been made available to their portal role.

Please note that self-registration requires initial configuration, including:

• Setting up a dedicated portal system user.
• Configuring portal user licensing.
• Configuring registration and password recovery notifications.
• Optionally customizing the registration and password recovery email templates.

Detailed setup instructions are available in the following Academy article:

https://academy.creatio.com/docs/8.x/creatio-apps/products/more-apps/po…

Hi Solem,

These steps need to be performed through a local development environment:

1. Set up the TypeScript SDK template project following Creatio's documentation
2. Run `npm run build` to compile and generate main.js
3. Place main.js in your package at: Packages/{YourPackage}/Files/src/mobile/{YourModuleName}/main.js
4. In Configuration → Actions → File System Development Mode → Update packages from file system
5. Compile and clear cache

You will also need to update your mobile manifest with two entries:

"RemoteModules": [
   {
       "name": "YourModuleName",
       "remoteName": "YourModuleName",
       "type": "remoteModule",
       "path": "src/mobile/YourModuleName/main.js"
   }
],
"CustomModules": [
   "YourModuleName"
]

Note: Both RemoteModules and CustomModules entries are required. If CustomModules is missing, the module will appear to load but none of your handlers will actually fire.

Also make sure the EnableMobileSDK feature flag is turned on at /0/Features

Hope that helps!