> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/whats-new/release-notes/previous-releases/2026/june-2026-release/june-2.0.md).

# June 2.0

{% hint style="warning" %}

This is a Custom Release. Feature availability depends on configuration and rollout status. Some features listed above may not be visible in your environment if they are part of a staged or custom deployment. Please contact your support representative to confirm enablement.
{% endhint %}

### Enhanced Default Search Type Selection for Pick Task Assignment

**Overview**

A new enhancement has been introduced to allow users to configure default **Search Type** selections for the **Pick Task Assignment** page through **WMS User Settings**. Once configured, the selected search type is automatically pre-populated whenever the Pick Task Assignment page is opened, eliminating the need for users to repeatedly select their preferred search mode.

**Key Enhancements**

* Added support to configure default **Search Type** values in **WMS > User Settings**.
* The selected search type is automatically applied when opening the **Pick Task Assignment** page.
* Supports all available search types, including:
  * Pick By Wave
  * Replenishments
  * Case Picks
  * Each Pick
  * Waiting For Replenishment
  * Manufacturing

**How It Works**

1. Navigate to **WMS -> User Settings**.
2. Under **Pick Task Assignment Defaults**, select the desired default **Search Type**.
3. Click **Update Setting** to save the configuration

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2F36JwAYK2mtZ3bzMJ7dC9%2Fimage.png?alt=media&amp;token=6ae81009-d29e-4e6b-bcd0-27a47a3ea540" alt=""><figcaption></figcaption></figure>

4. Open the **Pick Task Assignment** page. The configured search type, **Each Pick**, is automatically selected, and its corresponding tasks are displayed by default.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FYsv8P6vNmhNudjU8Hus6%2Fimage.png?alt=media&amp;token=ab657847-bc49-4d96-96af-50fd5e862b87" alt=""><figcaption></figcaption></figure>

5. Go to the **Wave Centre** in ERP and double-click the required wave to open the **Wave** subform. Then, click the **Search** icon under the **Action** column for the corresponding **Order#**.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2F33uaAjii79YXIIqo2P4V%2Fimage.png?alt=media&amp;token=defa721a-3186-4889-a848-133f13c2bd2d" alt=""><figcaption></figcaption></figure>

6. The **Wave Line Allocation** window opens, where you can view the **Pick Type** for the corresponding task.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2F5dIgDeqigMyzzt15VVF4%2Fimage.png?alt=media&amp;token=9555a829-a26b-4292-892c-926136278305" alt=""><figcaption></figcaption></figure>

***

### App Config: Use Signed Invoice For Email Queue

**Overview**

This enhancement introduces a new application configuration that allows the system to automatically attach the most recently signed invoice when an invoice is manually added to the Email Queue. If no signed invoice is available, the system attaches the standard invoice document instead.

***

**Configuration Details**

**App Config Name:** Use Signed Invoice For Email Queue

**Configuration Location: Menu → App Config → General → Use Signed Invoice For Email Queue**

***

**Functionality**

**When App Config Is Enabled**

* If a signed invoice exists for the selected invoice, the system attaches the most recently signed invoice document to the **Email Queue**.
* If no signed invoice exists, the system automatically attaches the standard invoice document.

***

**When App Config Is Disabled**

* The system always attaches the standard invoice document when the invoice is manually added to the Email Queue, regardless of whether a signed invoice exists.

***

**How It Works**

1. Navigate to **Menu → App Config → General** and enable the **Use Signed Invoice For Email Queue** app configuration.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FIbfiBhUAZkmSqNgRObno%2Fimage.png?alt=media&amp;token=9874545d-5a88-4de3-b22c-256ff77c2851" alt=""><figcaption></figcaption></figure>

2. Navigate to **Menu → Sales → Invoice** and create an invoice.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FpXGCbieIoapdzl9T9ywr%2Fimage.png?alt=media&amp;token=13bd7bd0-1c3f-4a0f-a94b-a9eb40e0d6f8" alt=""><figcaption></figcaption></figure>

3. Go to **Menu → Sales → Invoice Centre** and select the recently created invoice. Click the **header-level Options** menu and select **Print**.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FaD0pEGp9ZDGhRQ6MQvYw%2Fimage.png?alt=media&amp;token=bfef5260-52b5-46c3-926e-00fd6fc15c91" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FPla9sE1W8dClvnMAZc01%2Fimage.png?alt=media&amp;token=96b7a6ea-0e63-49c6-b567-881cbf797e90" alt=""><figcaption></figcaption></figure>

4. In the **Select Reporting Template** popup, select the document template and enable the **Capture Signature** toggle. Click on the **Capture Signature** option.&#x20;

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FXMqokiJFSXEYcJhDO50H%2Fimage.png?alt=media&amp;token=ee88d1fd-3cdc-46e8-b57c-81594fcb7618" alt=""><figcaption></figcaption></figure>

5. Enter the signer's name, capture the signature, and click **Save**.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FCRBrUhJ0jzicg4gAoLN4%2Fimage.png?alt=media&amp;token=1c74bba5-a201-45e5-927a-1808c33fe864" alt=""><figcaption></figcaption></figure>

6. Open the invoice. The signed invoice is visible under the **Signed Invoice(s)** tab and includes the signed report.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FsYApi5DouVs6fOifV23F%2Fimage.png?alt=media&amp;token=1fb3f835-721c-4ab7-8aeb-9be00090de75" alt=""><figcaption></figcaption></figure>

7. From the **header-level Options** menu, select **Add to Email Queue**.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FAe2xrOBZOlOxC7AEJkOZ%2Fimage.png?alt=media&amp;token=0d014601-402d-416e-9fc9-29edc78d6f68" alt=""><figcaption></figcaption></figure>

8. Select the required document template and email template, configure the recipient details if required, and click **Preview & Send**.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FGjqKCivwvV4ZJinmKXgq%2Fimage.png?alt=media&amp;token=03fee200-d1ca-4b76-a42f-22f4cfc91dc4" alt=""><figcaption></figcaption></figure>

9. The invoice is added to the **Email Queue** in the **Email Centre.** Send the selected invoice.&#x20;

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FVQDp7EQL7fHpSyqHYhoM%2Fimage.png?alt=media&amp;token=6257030f-a107-4749-8937-e0956f5f28ca" alt=""><figcaption></figcaption></figure>

If a signed invoice exists, the system attaches the signed invoice to the email. Otherwise, it attaches the standard invoice document.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2Fvuws1Wi26jbB7qKnTStA%2Fimage.png?alt=media&amp;token=9078dda0-89ff-4863-81d0-fec4c4e51695" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2FUZGDB4VkcN0QSxcZS7Tc%2Fimage.png?alt=media&amp;token=1ac31207-82f4-4fb4-bd9c-2d3df0062330" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This enhancement is applicable only when invoices are manually added to the Email Queue using the **Add to Email Queue** option. It does not affect invoices sent through any automated email processes.
{% 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.xorosoft.com/whats-new/release-notes/previous-releases/2026/june-2026-release/june-2.0.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.
