> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/inventory/gate-pass-manager/issue-against-new-gate-pass.md).

# Issue Against New Gate Pass

Logic ERP has corrected **Issue Against New Gate Pass** in **Gate Pass Manager**. The **Modify** list now holds only the gate passes made in this screen, and gate pass numbers keep their full prefix.

***

### **Step 1: Open the Screen**

* Navigate to **Inventory** and select **Gate Pass Manager**.
* Open **Issue Against New Gate Pass**.

***

### **What's corrected**

* **Modify** no longer lists the gate passes made in **Gate Pass Entry Against L.R.**, whether made with **L.R Selection** or **P.O Selection**. Those gate passes are opened and changed only from that screen, whose own **Modify** list shows just the gate passes made there for your current branch.
* Document prefixes longer than 4 characters are now saved in full. Earlier the prefix was cut to its first 4 characters.
* The save message now shows the gate pass number as it is saved, for example "Gate Pass G145 Saved Successfully". This is the number to type in **GPN Number** on the Purchase Challan or Purchase Voucher. Earlier the message showed **G-145**.


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/inventory/gate-pass-manager/issue-against-new-gate-pass.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.
