PDF is having empty white space in every page after upgrade from 8.2.3 to 8.5

Hello All,

We have recently upgraded from 8.2.3 to 8.5 after this upgrade all the pdf are having empty white spaces. Please suggest any possible fix.(Other than getting the HFix :slight_smile: )

Thanks

@KishoreYagnamurthy Any one having the same issue?

@KishoreYagnamurthy

Can you try the below and check:

  • Set the PDF with pyPDForientation set to “portrait/landscape” and check?
  • Set the parameter ‘pyHTMLDisableProcessing’ to “true” and check?

@KishoreYagnamurthy

Yes, we are having the same issue. 8.3.1 to 8.5.3 upgrade.

@TashikaS

I think you are mention about the “pyPDFSettings” data transform related values. Those are changed as you mentioned here, but result is same. Can you please let us know what is the next steps?

Below values are set and tested. No luck.

param.pyHTMLDisableProcessing=true

param.pyPDFPageOrientation =“portrait/landscape”

@Dhanusha Got it. Did you guys try any other alternative approaches to fix this issue other than working on paragraphs rules again?

@Dhanusha

Can you guy try this

Param.pyEnableSmartTableBreaks = false

@KishoreYagnamurthy

Hi Kishore

Did you got any resolution for this ?

@SuprasenaB Nope. we had to manually fix it in the code

@TashikaS Thanks for the response. Yes, we already had the pyPDForientation parameter set. I added pyHTMLDisableProcessing to true but there is no change.I still issues in all PDfs

@KishoreYagnamurthy

While tracer and all, I’ve taken a private checkout of “CL:@baseclass ID:GetWorkStyle RS:Pega-ProCom:08-01-01” and tried. So it seems okay. Therefore I m thinking issue is with our skin rule after upgrade. Sometimes, it might not inherited from the latest 8.5 changes.

I’ll add the finding is I could come through..

@KishoreYagnamurthy we are going to remove the Skin applicability from reports.

When we trace the session, I have observed,

  • When previous code run, it takes pzDesignerStudio skin rule
  • But now it takes application skin rule.

So actually we have to fix the application skin rule to avoid this gap. But now as a quick solution, we are going to remove the skin rule applicability from reports.

@Dhanusha Thanks for the reply. That would be a perfect alternative for us too. I just tried it by removing the reports checkboxes on the skin I did not see any change( Attached screenshot). Can you explain what were the steps you followed?

@TashikaS Any other suggestions to fix this issue?

@TashikaS What is the suggested way to fix this issue?

@TashikaS Yes, we are using paragraph rules with HTML code inside it. Ok I will try to submit a support request

@KishoreYagnamurthy

what was the manual fix ?

@TashikaS Thanks for the reply. I tried both values mentioned in the comment and screenshot No luck.

@KishoreYagnamurthy

There is nothing to do with skin changes. (Sorry if I confused you)

On report rule, you can add the tick for “Ignore application skin when exporting to PDF” (Data Access tab on report rule).

@Dhanusha Oh got it. It might not be applicable for our scenario we are referring to the data on the clipboard inside the paragraphs rules.