Question
TCS
IN
Last activity: 2 Oct 2025 22:37 EDT
PDF Parsing is not working for Pega Version 24.2.2 and above
I am trying to Parse PDF by creating EForm File and Map eForm rules, uploaded the PDF template into EForm File, created Activity to Parse PDF by using Java step to convert the base 64 into Bytes, used OOTB Activity "ExtractDataFromEForm".
Same is working fine for Pega Version 24.1.2, but its not working for pega versions 24.2.2 and above.
Pegasystems Inc.
GB
@MAHESHPRASADS ⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
This is a known issue with Pega version 24.2.2 and above. The PDF parsing functionality has been impacted due to changes in the platform. I recommend following the steps detailed below to manually create the necessary eForm rules and ensure compatibility with the updated platform.
Analysis
Specifically, the removal of certain functionalities and libraries in the newer versions has caused similar issues.
Proposed Solution
To resolve this issue, follow these steps:
@MAHESHPRASADS ⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
This is a known issue with Pega version 24.2.2 and above. The PDF parsing functionality has been impacted due to changes in the platform. I recommend following the steps detailed below to manually create the necessary eForm rules and ensure compatibility with the updated platform.
Analysis
Specifically, the removal of certain functionalities and libraries in the newer versions has caused similar issues.
Proposed Solution
To resolve this issue, follow these steps:
- Manually Create eForm Rules: Since the PDF to Eform wizard option has been removed in version 24.2.2, you will need to manually create both the eForm File rule and the Map eForm rule.
- eForm File Rule: Choose the appropriate class, upload your PDF form, and save the rule. Ensure the PDF is fillable.
- Map eForm Rule: Select the same class as the eForm file rule, choose the uploaded eForm file rule, and map each PDF field to a corresponding property.
- Check for Missing Libraries: Ensure that all necessary libraries are present. For example, the removal of the
soap-2.3.1.jarin version 8.8.2 caused issues, and similar removals might affect your version. - Use Updated Activities: Verify that the OOTB Activity
ExtractDataFromEFormis compatible with the new version. If not, consider using or creating a custom activity that handles the PDF parsing correctly. - Enable PerformFieldFlattening: If you encounter issues with fields not displaying correctly, enable the
PerformFieldFlatteningcheckbox in theGenerateEFormactivity.
Root Cause
The root cause of this issue is the removal and refactoring of certain functionalities and libraries in Pega version 24.2.2 and above. These changes have impacted the PDF parsing capabilities, requiring manual intervention and updates to the eForm rules and activities.
HCA Healthcare
US
Here’s a quick fix path. First check the PDF type: ExtractDataFromEForm only works with AcroForm fields; many 24.2.x failures are XFA PDFs. Convert/flatten the template to standard AcroForm (any PDF editor can do this), then recreate the EForm File rule from the converted PDF and re-save your Map eForm. In your activity, decode with Base64Util.decodeToBytes (avoid custom Java that might add BOM/encoding noise) and pass the raw byte array to ExtractDataFromEForm. Make sure the template is in the current ruleset version (not an older branch), clear caches/restart the node, and retest. If it still fails, check the logs for pdfbox errors; 24.2.x upgraded libraries are stricter about malformed form fields, so re-generate mappings after conversion. As a fallback, parse a small known-good AcroForm first to confirm the rule path, then swap back to your real template.