Hi Jude, better option to get help is to open an iService ticket to get specialist help here.

Just a high level:

1. make sure that the parameter you want to use are added via the URL expression on the mun item used to call the report  

2. then the parameter can used in the report manager definition and assigned

Also make sure the parameter id in the format expected. IRIS dates are usually in $Horolog format and not in yyyy-mm-dd as might be expected by LogiReports.

Hi,

Iris comes with a PDF render engine based on Apache FOP. This is though more used to create PDF documents from scratch than convert documents to pdf.

PDF render config documentation

Which is used in the now deprecated ZENReports %ZEN.Report.PrintServer - InterSystems IRIS Data Platform 2024.3 - including private class members

The other option is to make use of InterSystems Reports, but again this is for creating new pdfs from data contained in the database, not converting existing documents to pdf.

Option 2 is not totally correct.
The parameter [Startup] MaxIRISTempSizeAtStart=5000 will clear the IRISTemp database and shrink it to the size specified it will not prevent IRISTemp from growing further.
So you set the parameter and restart IRIS and the runaway IRISTemp database will be reset to 5000MB (per example)

To ensure IRISTemp is not taking over all your available space either relocate the DB to a dedicated volume or set the maximum DB size in SMP for the database. But this all has its own risk.

Hi Dmitrii,

The automated export of changed files can be handled by %Studio.SourceControl.File, this would export any changed file on save and import the latest from disk on checkout.

To automate import on a target system you can create a scheduled task that executes $system.OBJ.LoadDir regularly, this also per default compiles on load.