Page 1 of 1

ReportToPDFModule variables

Posted: Fri Dec 06, 2019 10:54 pm
by dmconsulting1
Not quite sure what it is looking for here. It has 5 unbound variables, I added a path and filename, but it doesn't report to either and it complains of unbound variables for the others. If I auto create and auto bind, it says:

Failed to set value '' to variable 'DeleteRanorexReport'.

So what values is it looking for? Why is it not posting the report to the path specified? I am not seeing much in the users guide as to what it is looking for with these variables.

Re: ReportToPDFModule variables

Posted: Mon Dec 09, 2019 10:44 pm
by dmconsulting1
I have set $ReportDestinationPath = 'c:\ESI\Reports\'

And added a copy to ReportTpPDFModule

File.Copy(pdfReportFilePath, Path.Combine(ReportDestinationPath,fileName));

This copies the PDF file to the ReportDestinationPath specified in the variable.

I still get warnings the other variables are not bound, but I am still unclear as to what they are looking to be bound to.

Re: ReportToPDFModule variables

Posted: Wed Dec 11, 2019 3:06 pm
by foals11
Hi,

on your first post, you receive this error because of a wrong parameter value.

I would recommend using the auto created parameters and module variables.
In my attached picture you can see, which values have to be set, to create a PDF report with a customized file name and directory path.
Afterwards, you shouldn't get any warnings.

regards,

Re: ReportToPDFModule variables

Posted: Fri Dec 27, 2019 3:24 pm
by weklein
We are now using the Ranorex.PDF.dll File for the PDF-Report-Generation. Hopefully this dll will work with further Ranorex-Versions.
Whitelisting this file is not likely to happen since we test within our standard client configuration, which is deployed for >10k Windows Desktops.
Yesterday we had the Ranorex Foundation Level Training and one of my collegues wanted to send his Ranorex-Test-Solution via Gmail. Sadly even Gmail detects the Ranorex.PDF.exe inside a ZIP as a Virus.

Maybe you find a solution for a variarity of costumers since a Filename .PDF.exe is likely to be detected by a range of anti-virus mechanisms?
Thanks
MyColes

Re: ReportToPDFModule variables

Posted: Fri Dec 27, 2019 7:02 pm
by mayo
I don't think there is any way around the anti-virus besides whitelisting or disabling it. You could also head over to the User Voice platform and leave a feature request, which is helpful to everyone.

-mayo

Re: ReportToPDFModule variables

Posted: Mon Jan 06, 2020 3:27 pm
by dmconsulting1
Ok, so I seem to be missing one of the variables now and I can't seem to recover it.

The Parameter ReportDestinationPath no longer has a variable. Did something change in the Automation Helpers?