Question
AARETE
US
Last activity: 7 Aug 2023 10:33 EDT
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 :-) )
Thanks
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Updated: 6 Jan 2022 15:01 EST
AARETE
US
@SuprasenaB correcting it with the CSS code
AARETE
US
@KishoreYagnamurthy Any one having the same issue?
Pegasystems Inc.
IN
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?
Updated: 15 Jun 2021 10:36 EDT
EvonSys Inc
US
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"
AARETE
US
@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
Updated: 15 Jun 2021 7:08 EDT
EvonSys Inc
US
Yes, we are having the same issue. 8.3.1 to 8.5.3 upgrade.
EvonSys Inc
US
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..
EvonSys Inc
US
@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.
AARETE
US
@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?
EvonSys Inc
US
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).
Pegasystems Inc.
IN
Pegasystems Inc.
IN
The section/HTML that you are passing is it having any HTML code/non-auto generated section? Can you try passing a simple section with a layout and check?
Other than this, I think we have tried all the options. I would suggest you raise an INC and mention all the above points as solutions attempted.
Pegasystems Inc.
US
Please reference this Question in your Support ticket so that our Engineers can review it and know what you've tried so far.
Also, let us know the ID and we can track the status as well.
Thank you!
VA government
US
AARETE
US
@SuprasenaB Nope. we had to manually fix it in the code
VA government
US
Accepted Solution
Updated: 6 Jan 2022 15:01 EST
AARETE
US
@SuprasenaB correcting it with the CSS code
Coforge
US
@KishoreYagnamurthy What was the CSS solution to this issue?