> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/changelogs/version-7/7-0-1.md).

# Version 7.0.1 Changelog (2019-08-20)

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

## New Features

* Added utility functions to ComboBoxWidget and ListBoxWidget which simplify reading and editing options. (GetOptions(), ReplaceOptions() and RemoveOption())

## Other Changes

Roughly categorized, not an exhaustive list.

#### Robustness:

* \[xod] Better support corrupt PDF content streams with mismatched BT and ET entries.
* \[xps] Fixed a potential crash when reading JPEG XR files on non-windows platforms.
* \[pdf] Fixed an issue with PDFViewCtrl.OpenURL error handling when losing internet connection while download is in progress.

#### Improvements:

* \[pdf] Adjusted ElementBuilder.CreateRect to support input rectangles that are not normalized.
* \[xps] Added basic detection for proprietary PhotoShop headers that impact jpeg scaling in XPS files.

#### Bugfixes:

* \[pdf] Adjusted XFDF import for Form Fields to properly construct missing fields and appearances.
* \[pdf] Fixed a problem with DigitalSignatureField.GetDocumentPermissions.
* \[pdf] Fixed filled Polyline rendering when there are line beginning/ending styles.
* \[pdf] Fixed a problem where per page XFDF export would sometimes not include all of the field attributes.
* \[xod] Fixed an uncommon issue where some completely masked graphics would be visible after ToXod conversion.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/core/changelogs/version-7/7-0-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.