> 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/ios/changelogs/version-7/v7-1-4-75416.md).

# Version 7.1.4.75416 Changelog (July 14th, 2020)

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

* Version: 7.1.4.75416
* Release Date: July 14th, 2020
* Built with Xcode 11.3.1 (11C505)

## New

* Annotations can now be selected and copied (but still not pasted) in read-only mode.
* A sticky note annotation's text content is also now viewable in read-only mode.
* Bookmark control ensures only one bookmark can be added per page.

## Bug fixes

* \[Collaboration] Fixes an issue where annotations couldn't be deleted by their author.
* Fixes an issue where certain Free Text annotation attributes were missing when exported to XFDF.
* Fixes an issue where opening a currently open document in another app could cause the document to be saved even when autosave was disabled.
* Fixes an issue where after editing a free text annotation, its fill colour would not be correctly reflected.
* Fixes an issue where editing the text of a callout annotation caused the text to be hidden.
* Fixes an issue where multiple annotations could be grouped together in read only mode.


---

# 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/ios/changelogs/version-7/v7-1-4-75416.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.