> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/release-notes/release-notes-q2-2025.md).

# Release Notes - Q2 2025

Known Bug with correction

* SharinPix Mobile App: Alert Box remaining on page when opening another mode on the SharinPix Mobile App
* SharinPix Album: Improved screen reader support by adding accessible label to delete button
* SharinPix Album: Fixed bug where pressing "Delete" triggered multiple image dialogs and bulk deletion
* SharinPix Form: Form Response not created due to batch not related to form
* SharinPix Form: Rich Text fields did not take the full width of the form
* SharinPix Form: Can view filled form on SharinPix Mobile App from Job page

New Features

* SharinPix Mobile App: Hide all Annotations after selecting to provide a more user-friendly interface to annotate on the image
* SharinPix Form: Prefilled Value for Question Elements
* SharinPix Form: Conditional Visibility on Form Element
* SharinPix Form: Comparative Functionality
* SharinPix PDF Form Builder: Prefilled Value for template-image for Photo Fields

{% hint style="warning" %}
**Note:**

Latest Version containing the above Bug Fixes and New Features:

* SharinPix Mobile App: v.6.47827
* SharinPix on Salesforce App Exchange: v.1.355
  {% endhint %}


---

# 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.sharinpix.com/release-notes/release-notes-q2-2025.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.