> 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/uwp/changelogs/version-7/v7-0-4.md).

# Version 7.0.4 Changelog (December 18, 2019)

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

Version: 7.0.4.73543

Release Date: December 18, 2019

### New Features

* UI support for selection and editing of multiple annotations with Multi-Select tool. You can resize, change border and background color, change opacity, delete, flatten the annotations together, and group the annotations.
* Undo & Redo tools.
* Programmatic support to show / hide individual tools in the AnnotationCommandBar / AnnotationToolBar. (`IsStickyNoteToolButtonVisible`, `IsHighlightToolButtonVisible`, `IsUnderlineToolButtonVisible`, `IsStrikeoutToolButtonVisible`, `IsSquigglyToolButtonVisible`, `IsStamperToolButtonVisible`, `IsSignatureToolButtonVisible`, `IsInkToolButtonVisible`, `IsEraserToolButtonVisible`, `IsMarkerToolButtonVisible`, `IsTextBoxToolButtonVisible`, `IsShapeToolsButtonVisible`, `IsPanToolsButtonVisible`, `IsMultiSelectToolButtonVisible`, `IsUndoRedoToolButtonVisible`, `IsSquareToolButtonVisible`, `IsCircleToolButtonVisible`, `IsLineToolButtonVisible`, `IsArrowToolButtonVisible`, `IsPolylineToolButtonVisible`, `IsPolygonToolButtonVisible`, `IsCloudToolButtonVisible`)
* Added IUndoRedoManager and SimpleUndoRedoManager in the PDFViewCtrlTools project.
* PDFViewCtrl has new API to support Undo Redo. (`EnableUndoRedo`, `Undo`, `Redo`, `TakeSnapshot`, `GetNextUndoInfo`, `GetNextRedoInfo`, `RevertAllChanges`)

### Improvements and Bugfixes

* Fix for a bug with Stamp annotation rotation.
* Fix for not being able to select cloudy annotation when outside edge (cloudy shape) is clicked.
* Other miscellaneous bug fixes.


---

# 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/uwp/changelogs/version-7/v7-0-4.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.