> For the complete documentation index, see [llms.txt](https://docs.novacura.com/marketplace-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/change-log/ifs-application-10.md).

# IFS Application 10

{% tabs %}
{% tab title="Flow Classic" %}

## 1.0.2.3 - 2025-02-26

### Added

* Adding **Count Inventory Part (Offline)** app

## 1.0.2.2 - 2024-09-06

### Fixed

* Register Arrivals - Recognizing more types of serialized parts

## 1.0.2 - 2022-10-25

### Fixed

* Serial Tracking at Receipt and Issue

## 1.0.1 - 2022-05-27

### Fixed

* Avoided direct table usage

## 1.0.0 - 2021-06-15

### Added

* Initial release
  {% endtab %}

{% tab title="Flow Connect" %}

## 1.0.2 - 2026-06-03

### Fixed

* Checkbox incorrectly passes value in script step
  * Count Handling Unit
  * Count HU per Count Report
  * Count Inventory Part
  * Count Part per Count Report
  * Create Handling Unit
  * Create Material Requisition Line
  * Delete Handling Unit
  * Modify Handling Unit
  * Reassign Handling Unit on Shipment
  * Receive Shop Order
  * Receive Shop Order Handling Unit

## 1.0.1 - 2025-12-11

### Fixed

* Report Picking of Parts - Temporary serials on non-serialized items

## 1.0.0 - 2025-03-01

### Migrated

Migrated below **Warehouse Management** app package from Flow Classic to Flow Connect

### Handling Unit Management

* Create Handling Unit
* Modify Handling Unit
* Delete Handling Unit
* Attach Part No to Handling Unit
* Unattached Part No to Handling Unit
* Change Parent Handling Unit

### Procurement

* Register Arrivals
* Attach Receipt to Handling Unit
* Unattach Receipt to Handling Unit
* Move Part into Receipt

### Warehouse Handling

* Find Inventory
* Move Inventory Part
* Move Handling Unit
* Count Inventory Part
* Count Handling Unit
* Count Part per Count Report
* Count HU per Count Report
* Issue Inventory Part
* Scrap Inventory Part
* Scrap Handling Unit
* Start Transport Task
* Process Part on Transport Task
* Process Handling Unit on Transport Task
* Receive Inventory Part from Transit
* Receive Handling Unit from Transit
* Create Material Requisition Line
* Issue Material Requisition Line
* Start Warehouse Task
* Park Warehouse Task

### Customer Order & Shipment

* Start Picking
* Report Picking of Parts
* Report Picking of Handling Units
* Deliver Customer Order
* Deliver Confirmation of Customer Order
* Process Shipment
* Pack into Handling Unit on Shipment
* Unpack from Handling Unit on Shipment
* Reassign Handling Unit on Shipment
* Return Handling Units from Shipment Inventory
* Move Parts Between Shipment Inventories
* Move Handling Units Between Shipment Inventories
* Scrap Parts in Shipment Inventory
* Scrap Handling Units in Shipment Inventory

### Maintenance

* Manual Issue Work Order
* Unplanned Issue Work Order
* Unissue Work Order

### Manufacturing

* Report Picking of Part SO Pick List
* Report Picking of HU SO Pick List
* Manual Issue Shop Order Part
* Manual Issue SO Handling Unit
* Receive Shop Order
* Receive Shop Order Handling Unit
* Receive Shop Order By Product

### Basic Data

* Change Default Site
  {% endtab %}
  {% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.novacura.com/marketplace-documentation/applications/explore-apps/ifs/warehouse-management/change-log/ifs-application-10.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.