diff --git a/Agents/AI ERP Agents/Inventory Fulfillment Agent/README.md b/Agents/AI ERP Agents/Inventory Fulfillment Agent/README.md index ed372447..116b78cb 100644 --- a/Agents/AI ERP Agents/Inventory Fulfillment Agent/README.md +++ b/Agents/AI ERP Agents/Inventory Fulfillment Agent/README.md @@ -3,317 +3,158 @@ > **Document:** Installation playbook > **Audience:** Customer implementation teams, Power Platform admins, F&O admins, and solution owners > **Status:** Deployment-ready working version -> **Last updated:** 06 May 2026 +> **Last updated:** 15 June 2026 -> [!WARNING] -> **Security note β€”** Do not store client secrets in this document. -> The IVS client secret must be entered directly into the relevant Power Platform environment variable. Do not paste, screenshot, email, or record the secret in this playbook or in implementation notes. +> **Before you start:** This guide assumes Inventory Visibility is being configured in a new environment. Save the Entra app registration values, IVS endpoint, environment ID, and default legal entity because they are required during solution import. ---- +## Prerequisites -## πŸ“‘ Table of Contents +1. **Set up a Microsoft Entra app registration for Inventory Visibility.** + Create the app registration and client secret used by Inventory Visibility. Save the Application/client ID, client secret value, and tenant ID. Use a separate app registration for each IVS environment. + References: [Register an application](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Β· [Add app credentials](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials) -1. [Purpose](#-purpose) -2. [How to Use This Playbook](#-how-to-use-this-playbook) -3. [What Gets Installed](#-what-gets-installed) -4. [Setup Summary](#-setup-summary) -5. [Prerequisites](#-prerequisites) -6. [Required Environment Values](#-required-environment-values) -7. [Deploy IFA](#-deploy-ifa) -8. [Validate IFA](#-validate-ifa) -9. [Troubleshooting](#-troubleshooting) -10. [Microsoft References](#-microsoft-references) +2. **Install and set up Inventory Visibility.** + Install the Dynamics 365 Inventory Visibility add-in and complete the Supply Chain Management setup. Confirm Inventory Visibility is installed, the integration is enabled, and inventory data is syncing. + Reference: [Install and set up Inventory Visibility](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-visibility-setup) ---- +3. **Set up Product Search for Inventory Visibility.** + Product search must be installed and configured before the agent can search for products. Confirm the required product data has synced and the product search API can return results. + Reference: [Set up product search for Inventory Visibility](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-visibility-product-search) -## 🎯 Purpose +4. **Optional: set up ATP.** + If users need Available-to-Promise responses, configure Inventory Visibility ATP. If ATP is not needed, disable the ATP tool after import and adjust the agent instructions. + Reference: [Inventory Visibility on-hand change schedules and ATP](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-visibility-available-to-promise) -This playbook describes how to get the **Inventory Fulfillment Agent (IFA)** running in a customer Power Platform environment. +5. **Enable the Finance and Operations MCP (required for transfer orders and sales orders).** + The transfer order and sales order child agents call Dynamics 365 F&O through the Model Context Protocol (MCP). Make sure the F&O MCP is enabled before testing these workflows. + Reference: [Dynamics 365 F&O Model Context Protocol](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/copilot/copilot-mcp) -IFA is delivered as a managed Power Platform solution containing: +## Download the Solution -- Copilot Studio agent components -- Inventory Visibility Service (IVS) tools -- Dynamics 365 Finance and Operations (F&O) MCP actions -- Power Automate cloud flows +Download the Inventory Fulfillment Agent solution ZIP from the FastTrack implementation assets repository. -Environment-specific values are supplied after import through environment variables and connection references. The intended outcome is a **published, validated agent** that can run inventory, reservation, transfer order, and sales order workflows according to the scope enabled for the customer environment. +[Inventory Fulfillment Agent on GitHub](https://github.com/microsoft/Dynamics-365-FastTrack-Implementation-Assets/tree/master/Agents/AI%20ERP%20Agents/Inventory%20Fulfillment%20Agent) ---- +Download the solution `.zip` file. **Do not extract it before importing.** -## 🧭 How to Use This Playbook +## Import the Solution -| Section | Use it for | -| --- | --- | -| [What Gets Installed](#-what-gets-installed) | Confirm the imported solution components and ownership boundaries. | -| [Setup Summary](#-setup-summary) | Understand the deployment sequence before starting. | -| [Prerequisites](#-prerequisites) | Confirm licensing, access, Power Platform, IVS, and F&O MCP readiness. | -| [Required Environment Values](#-required-environment-values) | Collect the values needed for variables, references, and validation. | -| [Deploy IFA](#-deploy-ifa) | Run the import and configuration steps with exit checks. | -| [Validate IFA](#-validate-ifa) | Test IVS, Copilot Studio, reservation, and F&O MCP behaviours. | -| [Troubleshooting](#-troubleshooting) | Map common symptoms to likely causes and corrective action. | -| [Microsoft References](#-microsoft-references) | Use official Microsoft documentation for supporting detail. | - ---- - -## πŸ“¦ What Gets Installed - -| Component area | Included items | -| --- | --- | -| **Copilot Studio agent** | Inventory Fulfillment Agent and child agents for order workflows. | -| **Agent actions** | IVS inventory actions and Dynamics 365 F&O MCP actions. | -| **Cloud flows** | IVS token, inventory, product search, reservation, and unreservation flows. | -| **Environment variables** | IVS tenant, app registration, endpoint, scope, and environment values. | -| **Connection references** | Dynamics 365 Finance and Operations connector reference. | -| **Knowledge** | Fulfillment proposal knowledge file, where included in the package. | - ---- - -## πŸš€ Setup Summary - -1. Confirm Copilot Studio, Power Platform, IVS, and F&O MCP prerequisites. -2. Import the IFA Power Platform solution into the target environment. -3. Populate the IVS environment variables with customer-specific values. -4. Configure the Dynamics 365 F&O connection reference. -5. Turn on **Get IVS Access Token**, then turn on the dependent IVS flows. -6. Validate IVS, Copilot Studio, and F&O MCP calls with known customer data. -7. Publish the agent β€” or leave it explicitly ready for customer-controlled publishing. - ---- - -## βœ… Prerequisites - -Complete these checks before import. Treat any failed prerequisite as a deployment blocker unless the scope has been explicitly reduced. - -### Licensing - -| Area | Requirement | -| --- | --- | -| Copilot Studio | Environment has entitlement to create, configure, test, and publish the agent. | -| Power Platform & Power Automate | Installer can import solutions, configure flows, and use required connectors. | -| Dynamics 365 F&O | Users invoking F&O operations have appropriate licensing and security access. | -| MCP usage | Review current F&O MCP and Copilot Studio credit guidance where relevant. | - -### Access - -| System | Required access | -| --- | --- | -| Power Platform | Import solution, update environment variables, configure connection references, turn on flows, and publish customisations. | -| Copilot Studio | Open, test, configure, and publish the imported agent. | -| Power Automate | Turn on flows and inspect run history. | -| Microsoft Entra | Read app registration details and create or rotate the IVS credential if needed. | -| Dynamics 365 F&O | Configure or validate MCP access and run F&O operations used by the agent. | - -### Power Platform Environment +1. Go to Power Apps at [make.powerapps.com](https://make.powerapps.com). +2. Select the target environment. +3. Go to **Solutions**. +4. Select **Import solution**. +5. Browse to the downloaded `.zip` file. +6. Select **Next**. +7. If prompted for a Dynamics 365 Finance and Operations connection, select or create the connection used by the order child agents. +8. Enter the environment variable values listed below. +9. Select **Import**. -| Requirement | Check | -| --- | --- | -| Target environment selected | Installer is in the correct Power Platform environment before import. | -| Dataverse enabled | Environment supports solutions, variables, references, flows, and Copilot Studio. | -| Copilot Studio available | Agent can be opened in Copilot Studio for the target environment. | -| Solution import allowed | Installer can import a Power Platform solution package. | - -### Inventory Visibility Service +Reference: [Import solutions in Power Platform](https://learn.microsoft.com/en-us/power-apps/maker/data-platform/import-update-export-solutions) -| Requirement | Check | -| --- | --- | -| Inventory Visibility installed | Confirm in Lifecycle Services or Power Platform admin centre. | -| Environment linking correct | Check F&O / Dataverse linking mismatch warnings where applicable. | -| IVS endpoint known | Base URL and IVS environment ID are available. | -| Entra app registration exists | Tenant ID and application client ID are available. | -| App credential valid | Client secret exists, is not expired, and can acquire a token. | -| IVS data exists | At least one known item / site / warehouse combination can be used for validation. | +## Environment Variables -### Finance and Operations MCP - -| Requirement | Check | -| --- | --- | -| Product version | F&O version satisfies the current MCP prerequisite. The supplied guidance states **at least 10.0.47**. | -| Environment tier | Target environment is **Tier 2 or above**, or Unified Developer Environment. | -| MCP feature | Dynamics 365 ERP Model Context Protocol server feature is enabled. | -| Allowed MCP client | Copilot Studio is allowed as an MCP client in F&O. | -| Security access | Connection user has access to required data entities, forms, and actions. | +During import, enter the values for the target environment. The table below explains what each value is and where it normally comes from. ---- - -## πŸ”§ Required Environment Values - -> [!IMPORTANT] -> **Before you start β€”** Collect these values before solution import where possible. Leave the IVS client secret out of written notes; enter it directly into the environment variable value field. - -| Value | Used for | Notes | -| --- | --- | --- | -| Power Platform environment name | Confirm import target. | Example: `D365Commerce`. | -| Dataverse environment ID | Support and diagnostics. | Power Platform environment GUID. | -| F&O environment URL | F&O connector and MCP access. | Customer-specific F&O URL. | -| F&O product version | MCP readiness. | Must satisfy current MCP prerequisite. | -| F&O legal entity | IVS and order operations. | Example: `USRT`. | -| IVS base URL | IVS HTTP calls. | Environment-specific IVS endpoint. | -| IVS environment ID | IVS route and security token context. | Confirm expected IVS / F&O environment ID. | -| IVS tenant ID | Entra token request. | Tenant owning the IVS app registration. | -| IVS client ID | Entra token request. | Application client ID. | -| **IVS client secret** | Entra token request. | **Enter securely into the environment variable. Do not record in notes.** | -| IVS scope | Entra token request. | Example: `/.default`. | -| IVS security scope | IVS security token exchange. | Example: `https://inventoryservice.operations365.dynamics.com/.default`. | -| Test item ID | Validation. | Known item with IVS data. | -| Test site ID | Validation. | Required for ATP and reservation checks. | -| Test warehouse / location ID | Validation. | Maps to IVS `locationId`. | -| Test customer account | Sales order validation. | Required only if sales order flow is validated. | -| Transfer warehouses | Transfer order validation. | Source and destination warehouses must differ. | - ---- - -## πŸ› οΈ Deploy IFA - -### Step 1 β€” Import the Solution - -| # | Action | -| :-: | --- | -| 1 | Open the Power Apps maker portal. | -| 2 | Select the target Power Platform environment. | -| 3 | Open **Solutions**. | -| 4 | Select **Import solution**. | -| 5 | Select the IFA solution package. | -| 6 | Review the solution name, publisher, version, and package type. | -| 7 | Resolve dependency warnings. | -| 8 | Select or create required connections when prompted. | -| 9 | Enter required environment variable values if prompted. | -| 10 | Start the import and wait for completion. | - -> βœ… **Exit check β€”** The Inventory Fulfillment Agent solution appears in the target environment. - ---- - -### Step 2 β€” Configure IVS Environment Variables - -| # | Action | -| :-: | --- | -| 1 | Open the imported Inventory Fulfilment Agent solution. | -| 2 | Select **Environment variables**. | -| 3 | Update the IVS variables with customer-specific values. | -| 4 | Resolve every environment variable warning. | -| 5 | Save changes. | -| 6 | Select **Publish all customisations**. | - -> βœ… **Exit check β€”** The solution overview no longer reports missing required environment variable values. - -#### Expected IVS Variables - -| Display name | Typical logical name | Required value | +| Environment variable | What to enter | Where to get it | | --- | --- | --- | -| `IVS_BaseUrl` | `ftc_IVS_BaseUrl` or `new_IVS_BaseUrl` | IVS base endpoint URL. | -| `IVS_ClientId` | `ftc_IVS_ClientId` or `new_IVS_ClientId` | Entra application client ID. | -| `IVS_ClientSecret` | `ftc_IVS_ClientSecret` or `new_IVS_ClientSecret` | Entra app client secret. | -| `IVS_EnvironmentId` | `ftc_IVS_EnvironmentId` or `new_IVS_EnvironmentId` | IVS / F&O environment ID. | -| `IVS_Scope` | `ftc_IVS_Scope` or `new_IVS_Scope` | Entra token request scope. | -| `IVS_TenantId` | `ftc_IVS_TenantId` or `new_IVS_TenantId` | Microsoft Entra tenant ID. | -| `IVS_SecurityScope` | `new_IVS_SecurityScope`, if present | IVS security token exchange scope. | +| IVS_TenantId | Microsoft Entra tenant ID used by the IVS app registration. | Microsoft Entra app registration or Azure tenant overview. | +| IVS Inventory Visibility Endpoint | Inventory Visibility endpoint, for example `https://inventoryservice..gateway.prod.island.powerapps.com`. | Inventory Visibility setup or endpoint details for the installed IVS add-in. | +| IVS Client ID | Application/client ID from the Entra app registration. | Microsoft Entra app registration overview. | +| IVS Client Secret | Client secret **value** from the app registration (not the secret ID). Enter directly into the variable; do not record elsewhere. | Microsoft Entra app registration secret created for IVS. | +| IVS_EnvironmentId | IVS/F&O environment GUID used by the Inventory Visibility API route. | Dynamics 365 / IVS environment details. | +| IVS Default Legal Entity | Default company/legal entity code, for example `usrt` or `usmf`. | Dynamics 365 Finance and Operations legal entity setup. | ---- +## Turn On the Cloud Flows -### Step 3 β€” Configure the F&O Connection Reference +Managed solutions may import cloud flows in a deactivated state. Turn them on in this order β€” the access-token flow **must** be on first because the others depend on it. -| # | Action | -| :-: | --- | -| 1 | In the solution, select **Connection references**. | -| 2 | Open the Dynamics 365 F&O connection reference. | -| 3 | Bind it to a valid Dynamics 365 F&O connection. | -| 4 | Confirm the connection points to the correct F&O environment. | -| 5 | Save the connection reference. | +1. **Get IVS Access Token** β€” turn on first; confirm a successful run in the flow run history. +2. IVS ATP / Inventory Check +3. IVS Product Search +4. IVS Onhand Reserve +5. IVS Onhand Unreserve -> βœ… **Exit check β€”** The connection reference has a valid connection and no warning is shown. +> If the agent returns token or authentication errors during testing, this step (or the environment variables above) is the usual cause. -#### Connection Reference +## Test the Agent -| Connection reference | Connector | -| --- | --- | -| `cr91d_agent9_4ET9z6.shared_dynamicsax.shared-dynamicsax-96e68f2b-5d16-41f7-919c-77b16415d9a9` | `/providers/Microsoft.PowerApps/apis/shared_dynamicsax` | - ---- - -### Step 4 β€” Turn On Cloud Flows +After import completes, turn on the flows, then open the agent in Copilot Studio and test the main capabilities. -Turn on **Get IVS Access Token** first. Then turn on the dependent IVS flows in order. +> **Note:** These test steps assume the agent is being tested against **Contoso Demo data**. Substitute your own item, site, warehouse, and customer values when testing other environments. -| Order | Flow | Check | -| :-: | --- | --- | -| 1 | Get IVS Access Token | Flow turns on and token validation succeeds. | -| 2 | IVS ATP Inventory Check v2 *(or IVS inventory check flow)* | Flow turns on with no configuration errors. | -| 3 | IVS Product Search | Flow turns on with no configuration errors. | -| 4 | IVS Onhand Reserve v2 | Flow turns on with no configuration errors. | -| 5 | IVS Onhand Unreserve v2 | Flow turns on with no configuration errors. | +- Search for product 81327 +- Check stock for item 81327 +- Check ATP for item 81327 at site central warehouse dc-central +- Reserve 2 of item 81327 at site central warehouse dc-central +- Create a transfer order for item 81327 from warehouse houston to warehouse dc-central quantity 1 +- Create a sales order for customer US-001 for item 81327 quantity 2 -> βœ… **Exit check β€”** All required flows are on, and **Get IVS Access Token** has a successful run history entry. +## Publish the Agent ---- +When validation has passed (and F&O MCP validation has passed if transfer/sales order workflows are in scope), publish the agent in Copilot Studio β€” or leave it explicitly ready for customer-controlled publishing. Configure channels if channel deployment is in scope. -### Step 5 β€” Open the Agent in Copilot Studio +## Capabilities -| # | Action | -| :-: | --- | -| 1 | Open Copilot Studio. | -| 2 | Select the target environment. | -| 3 | Open **Inventory Fulfillment Agent**. | -| 4 | Confirm the imported actions, child agents, topics, and knowledge are present. | -| 5 | Use test chat to confirm the agent can select IVS actions and F&O child agents. | +The agent supports the following business tasks: -> βœ… **Exit check β€”** The agent opens in Copilot Studio and can invoke the expected tools in test chat. +- Product search +- On-hand inventory checks +- ATP checks +- Soft reservations +- Unreservation +- Transfer order creation +- Sales order creation ---- +## Tools and Child Agents -### Step 6 β€” Publish the Agent +IVS actions are implemented as tools. A tool is a specific callable action, such as checking inventory, searching products, reserving stock, or unreserving stock. -| # | Action | -| :-: | --- | -| 1 | Confirm IVS validation has passed. | -| 2 | Confirm F&O MCP validation has passed if transfer order or sales order workflows are in scope. | -| 3 | Publish the agent. | -| 4 | Configure channels if channel deployment is in scope. | +Transfer orders and sales orders are handled by child agents. A child agent is used for a more complex process that may require multiple steps, such as summarising the request, asking for confirmation, creating a header, and then creating lines. -> βœ… **Exit check β€”** The agent is published or explicitly left ready for customer-controlled publishing. +## Customizing the Agent ---- +You can modify the agent after import to match the capabilities you want to expose. -## πŸ§ͺ Validate IFA +- If you do not use ATP, disable the ATP tool and remove ATP references from the instructions. +- If you do not want users to create reservations, disable the reserve and unreserve tools. +- If you only want inventory lookup, disable the transfer order and sales order child agents. +- Adjust the instructions to match your company terminology, warehouse naming, fulfilment rules, and support model. -Use known customer data for validation. Run only the scenarios that are in scope. - -| Area | Prompt pattern | Expected result | -| --- | --- | --- | -| **Product search** | *"Find product `` in ``."* | Agent returns matching products or asks one focused clarification question. | -| **On-hand inventory** | *"Check on-hand inventory for item `` in site `` warehouse ``."* | Agent calls IVS and reports current inventory. | -| **ATP** | *"Check ATP for item `` in site `` warehouse `` for the next 7 days."* | Agent calls IVS ATP and reports projected availability. | -| **Reserve** | *"Reserve `` of item `` at site `` warehouse ``."* | Agent asks for confirmation before reservation and returns reservation ID on success. | -| **Unreserve** | *"Unreserve reservation `` for item `` at site `` warehouse `` quantity ``."* | Agent asks for confirmation and reports unreservation result. | -| **Transfer order** | *"Create a transfer order in `` from `` to `` for `` of item ``."* | Agent routes to Transfer Order Agent and uses F&O MCP after confirmation. | -| **Sales order** | *"Create a sales order in `` for customer `` for `` of item ``."* | Agent routes to Sales Order Agent and uses F&O MCP after confirmation. | - ---- - -## 🩺 Troubleshooting +## Troubleshooting | Symptom | Likely cause | Action | | --- | --- | --- | -| `AADSTS7000222` in `Get_Access_Token` | Entra client secret is expired. | Create a new app credential, update `IVS_ClientSecret`, publish, and rerun **Get IVS Access Token**. | -| `401 invalid_client` in token flow | Wrong client secret, wrong client ID, wrong tenant, or expired credential. | Validate tenant ID, client ID, secret, and credential expiry in Entra. | -| `Get_Access_Token` succeeds but `Get_IVS_Token` fails | IVS security scope, environment ID, or service principal access is wrong. | Validate `IVS_SecurityScope`, `IVS_EnvironmentId`, IVS setup, and app permissions. | -| IVS flow reaches HTTP action but inventory call fails | Wrong IVS base URL / environment ID, IVS not installed, or item / dimension data missing. | Confirm endpoint values and test known IVS data. | -| Flow cannot be turned on | Missing connection, missing environment variable, invalid child flow reference, or insufficient permission. | Fix connection references and environment variables, then turn on **Get IVS Access Token** before dependent flows. | -| Agent selects IVS action but missing values reach the flow | Action input mapping or Copilot Studio tool binding is incomplete. | Inspect action inputs and ensure required flow trigger inputs are exposed to the agent. | -| F&O MCP calls fail with access denied | Connection user lacks F&O security permissions or MCP client is not allowed. | Validate F&O security roles and **Allowed MCP Clients** configuration. | -| Solution import fails | Missing dependency or insufficient import privilege. | Download import log, resolve dependency, and retry with sufficient Power Platform permissions. | - ---- - -## πŸ“š Microsoft References +| `AADSTS7000222` in Get IVS Access Token | Entra client secret is expired. | Create a new app credential, update the client secret variable, publish, and rerun Get IVS Access Token. | +| `401 invalid_client` in token flow | Wrong client secret, client ID, tenant, or expired credential. | Validate tenant ID, client ID, secret value, and credential expiry in Entra. | +| Access token succeeds but IVS token fails | Wrong environment ID, or service principal access. | Validate the environment ID, IVS setup, and app permissions. | +| IVS HTTP call reached but inventory call fails | Wrong endpoint URL / environment ID, IVS not installed, or item/dimension data missing. | Confirm endpoint values and test with known IVS data. | +| A flow cannot be turned on | Missing connection, missing environment variable, or insufficient permission. | Fix connection references and variables, then turn on Get IVS Access Token before the dependent flows. | +| F&O MCP calls fail with access denied | Connection user lacks F&O security permissions, or the MCP client is not allowed. | Validate F&O security roles and the Allowed MCP Clients configuration. | +| Solution import fails | Missing dependency or insufficient import privilege. | Download the import log, resolve the dependency, and retry with sufficient permissions. | + +## Quick Setup Checklist + +- [ ] Entra app registration created and client secret saved securely (not in notes). +- [ ] Inventory Visibility installed and configured. +- [ ] Product Search configured and synced. +- [ ] ATP configured if required. +- [ ] F&O MCP prerequisites met (if transfer/sales orders are in scope). +- [ ] Solution ZIP downloaded from GitHub. +- [ ] Finance and Operations connection selected during import. +- [ ] Environment variables entered for the target environment. +- [ ] Cloud flows turned on (Get IVS Access Token first). +- [ ] Agent tested in Copilot Studio. +- [ ] Agent published and ready for end-user consumption. + +## Microsoft References | Area | Reference | | --- | --- | -| Copilot Studio licensing and access | | -| Power Platform solution import | | -| Environment variables | | -| Connection references | | -| Inventory Visibility setup | | -| Microsoft Entra app registration | | -| Microsoft Entra app credentials | | -| Dynamics 365 F&O MCP | | +| Copilot Studio licensing and access | https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-licensing-subscriptions | +| Power Platform solution import | https://learn.microsoft.com/en-us/power-apps/maker/data-platform/import-update-export-solutions | +| Environment variables | https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables | +| Connection references | https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-connection-reference | +| Inventory Visibility setup | https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/inventory-visibility-setup | +| Microsoft Entra app registration | https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app | +| Microsoft Entra app credentials | https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials | +| Dynamics 365 F&O MCP | https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/copilot/copilot-mcp | diff --git a/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/InventoryFulfillmentAgent_V1_1_0_0_6.zip b/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/InventoryFulfillmentAgent_V1_1_0_0_7.zip similarity index 54% rename from Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/InventoryFulfillmentAgent_V1_1_0_0_6.zip rename to Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/InventoryFulfillmentAgent_V1_1_0_0_7.zip index a137bbf4..749506b0 100644 Binary files a/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/InventoryFulfillmentAgent_V1_1_0_0_6.zip and b/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/InventoryFulfillmentAgent_V1_1_0_0_7.zip differ diff --git a/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/README.md b/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/README.md index 57269a36..9ce975e3 100644 --- a/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/README.md +++ b/Agents/AI ERP Agents/Inventory Fulfillment Agent/Solutions/README.md @@ -9,3 +9,15 @@ Welcome to the Inventory Fulfillment Agent template. To get started, follow the This solution is provided as-is. Bugs, feature addition/modification requests, and other changes are the responsibility of the end-user. Always thoroughly test components in a non-prod environment. + +## Changes + +### Inventory Fulfillment Agent v1.0.0.7 + +* Fixed IVS token retrieval for environments that require the documented security service redirect flow. +* Added environment variable support for the default legal entity/company. +* Updated IVS tool calls to use the configured legal entity automatically. +* Fixed on-hand quantity mapping for current IVS response fields, including total on-hand, available to reserve, and total available. +* Improved handling for empty IVS/product search results so β€œno records found” is reported cleanly instead of as an error. +* Removed the previous helper flow for legal entity lookup and simplified the tool configuration. +* Kept solution import compatibility as an update to the existing Inventory Fulfillment Agent solution.