- Removing an ending bracket from a Data Grid Field caused the entire field to be ignored by the parser, so the original rule string showed up in the version. This is better than the old/misleading error message because it would show a doc developer exactly where the issue is, but since ASPOSE gave no indication that there was an error, this could easily be missed by user (especially in large documents like EOCs) unless they specifically searched for something like [[RuleID= in their versions.
Removing a caret from a DG field resulted in the version not pulling any data for this field. Again, since there was no indication via an error messaASPOSE-extract-part-of-the-document.zip (13.7 KB)
ge that there was an issue with any DG fields, this could easily be missed.
Known issue: When variable content appears at the end of a table row, versions often contain an extra line break at the end of the cell, even if there is not one present in the template. This can create formatting issues or the need for manual deletion for document developers.
Testing Results: We flagged areas within the template where this issue may occur and found that no extra line breaks were present in the versions after testing the template.
Known issue: If a template has an IF statement directly following an ENDIF statement within a table row, a number of issues parsing issues may occur. Console APP (.zip) and word documents is attached to simulate the situation.
RE ASPOSE Testing Results.zip (1.1 MB)