XFA Form Support and Limitations Are Not Sufficiently Explained - #801
Open
dessyordanova wants to merge 1 commit into
Open
XFA Form Support and Limitations Are Not Sufficiently Explained#801dessyordanova wants to merge 1 commit into
dessyordanova wants to merge 1 commit into
Conversation
Collaborator
Author
|
@YoanKar , please review the content addition, and if you decide to merge the changes, extract the embedded code snippets from the MD file before merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Priority: High
Confidence: 9/10
Missing Functionality:
The source contains XFA form model support and an export setting controlling whether XFA content is exported. Users need to know how XFA is imported, represented, preserved, and affected by
ShouldExportXfa.Evidence Found in Code:
Documents/Fixed/Core/Model/InteractiveForms/XfaCollection.csDocuments/Fixed/Core/Model/InteractiveForms/AcroForm.csDocuments/Fixed/Core/FormatProviders/Pdf/Export/PdfExportSettings.csDocuments/Fixed/Core/FormatProviders/Pdf/Import/PdfImportSettings.csDocuments/Fixed/Tests/Import/Current Documentation Status:
Missing as a focused topic. The settings article mentions
ShouldExportXfa, but there is no XFA model, workflow, compatibility, or limitation article.Remediation Action:
libraries/radpdfprocessing/features/interactive-forms/xfa.mdShouldExportXfa, supported scenarios, unsupported constructs, and interaction with AcroForm fields and compliance.Recommended Documentation:
Provide a small inspection/export example and a clear warning that XFA preservation is not equivalent to full authoring or rendering support.
Business/User Impact:
Enterprise PDF forms frequently use XFA. Users may unintentionally strip or mis-handle form data during import/export without knowing the setting and support boundary.