Skip to content

made links locale agnostic #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Hugo Bernier (hugoabernier) wants to merge 1 commit into
base: master
Choose a base branch
from
Open

made links locale agnostic #551

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions Agents/AI ERP Agents/Sales Order Agent/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,12 +106,12 @@ For implementing deterministic sales order specific validation rules, as well as
# ✅ Prerequisites for installing the Sales Order Agent solution
- Connected Dataverse environment with an environment with finance and operations apps. To confirm this, you can check in the Power Platform Admin Portal for a given environment that there is a corresponding link to Dynamics 365.
- The user who installs the Sales Order Agent solution must be a licensed user in Dynamics 365.
- Dataverse virtual tables enabled: Released products V2 (mserp), Customers V3 (mserp). Learn more about how to enable virtual tables in Dataverse at https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/power-platform/enable-virtual-entities.
- Dataverse virtual tables enabled: Released products V2 (mserp), Customers V3 (mserp). Learn more about how to enable virtual tables in Dataverse at https://learn.microsoft.com/dynamics365/fin-ops-core/dev-itpro/power-platform/enable-virtual-entities.
- Sales Order agent solution imported and agent configured as indicated in the next section.
- System Administrator role for solution import and agent configuration.
- Manual Reviewers should be assigned the Sales Order Agent Reviewer security role after the solution is imported.
- During solution import, ensure to provide values for either **a personal mailbox or a shared mailbox to monitor, the mailbox folder to monitor, the company code (for the sample file you can use usmf) and a reviewer email address**. After solution import, the corresponding environment variables can be updated from the context of an unmanaged solution.
- Please ensure that the environment where the agent is running either has Copilot Studio credits assigned, or there is a pay as you go billing plan in place. For more details, please see https://learn.microsoft.com/en-us/power-platform/admin/manage-copilot-studio-messages-capacity?tabs=new.
- Please ensure that the environment where the agent is running either has Copilot Studio credits assigned, or there is a pay as you go billing plan in place. For more details, please see https://learn.microsoft.com/power-platform/admin/manage-copilot-studio-messages-capacity?tabs=new.

**TIP**: If you require to monitor other folders than Inbox, please ensure there is a rule in place to route the emails automatically to the respective folder. For example, for a subfolder SalesOrder, you'd need to provide the value Inbox/SalesOrder for the folder to monitor.

Expand Down Expand Up @@ -149,7 +149,7 @@ Import the Sales Order Agent solution from the Solutions folder and please consi
# ✅ Sales Order Agent installation via store
After installing the solution containing the sales order agent and components in Dataverse, there are several post-installation and configuration steps necessary. If you face issues please dont hesitate to reach out by filling out this form https://forms.office.com/r/BzUfaL89da :

- **1. Create an unmanaged solution** - once the package from the store is succesfully deployed you will see two managed solutions installed in your Dataverse environment. Please proceed to create a new **unmanaged** solution to store the components which need to be configured. For step by step guidance, please see https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-solution.
- **1. Create an unmanaged solution** - once the package from the store is succesfully deployed you will see two managed solutions installed in your Dataverse environment. Please proceed to create a new **unmanaged** solution to store the components which need to be configured. For step by step guidance, please see https://learn.microsoft.com/power-apps/maker/data-platform/create-solution.

- **2. Add environment variables to the unmanaged solution** - once you create your unmanaged solution, open it, and click Add Existing - > More - > Environment variable:
![addvariables1](images/envvariables_1.png)
Expand All @@ -174,7 +174,7 @@ After installing the solution containing the sales order agent and components in
- After enabling the flows, we should see a status of On (except for the mailbox trigger flow depending on if you use shared and/or personal mailbox for monitoring)
![addvariables7](images/cloudflows_2.png)

- **6. Confirm product and customers Dataverse virtual tables are enabled** - follow instructions detailed at this page https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/power-platform/enable-virtual-entities. In order to open the Classic Advanced Find, you can also open the Power Platform Environment Settings app, click on Search in the toolbar then click on “Search for rows in a table using advanced filters”:
- **6. Confirm product and customers Dataverse virtual tables are enabled** - follow instructions detailed at this page https://learn.microsoft.com/dynamics365/fin-ops-core/dev-itpro/power-platform/enable-virtual-entities. In order to open the Classic Advanced Find, you can also open the Power Platform Environment Settings app, click on Search in the toolbar then click on “Search for rows in a table using advanced filters”:
![addvariables8](images/virtualtables_1.png)
- From the left corner, click on Switch to Classic
![addvariables9](images/virtualtables_2.png)
Expand All @@ -201,7 +201,7 @@ After installing the solution containing the sales order agent and components in
**8. Publish the Sales Order Agent** - open copilotstudio.microsoft.com, select the environment, in the list of agents find SalesOrderAgent, open the agent and press Publish button
![addvariables16](images/publishagent.png)

**9.Billing setup** – the agent is going to consume Copilot Studio credits – depending on the complexity and size of the documents parsed it can consume around 30 to 80 credits (1 credit = 0.01$) per attachment processed. Please ensure that the environment where the agent is running either has Copilot Studio credits assigned, or there is a pay as you go billing plan in place. For more details, please see https://learn.microsoft.com/en-us/power-platform/admin/manage-copilot-studio-messages-capacity?tabs=new.
**9.Billing setup** – the agent is going to consume Copilot Studio credits – depending on the complexity and size of the documents parsed it can consume around 30 to 80 credits (1 credit = 0.01$) per attachment processed. Please ensure that the environment where the agent is running either has Copilot Studio credits assigned, or there is a pay as you go billing plan in place. For more details, please see https://learn.microsoft.com/power-platform/admin/manage-copilot-studio-messages-capacity?tabs=new.

**10. Test the agent** - send an email with attachment to the configured mailbox address.

Expand All @@ -220,9 +220,9 @@ After installing the solution containing the sales order agent and components in
- The processing of email attachments, the extracted sales order data validations and processing are asyncronous operations.
- The agent is going to consume Copilot Studio credits. Depending on the complexity and size of the documents parsed it can consume around 30 to 80 credits (1 credit = 0.01$) per attachment processed.
- The agent only processes the email attachments: pdf by default, and optionally also images (png,jpeg,jpg) (controlled with environment variable)
- The agent uses AI Builder custom GPT prompts for document extraction. The GPT prompts support documents with less than 50 pages, for the full list of limitations please see https://learn.microsoft.com/en-us/ai-builder/add-inputs-prompt#limitations
- The agent uses Office 365 connectors for monitoring the mailboxes, please see the limitations https://learn.microsoft.com/en-us/connectors/office365/#limits
- Other Copilot Studio limitations https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-quotas
- The agent uses AI Builder custom GPT prompts for document extraction. The GPT prompts support documents with less than 50 pages, for the full list of limitations please see https://learn.microsoft.com/ai-builder/add-inputs-prompt#limitations
- The agent uses Office 365 connectors for monitoring the mailboxes, please see the limitations https://learn.microsoft.com/connectors/office365/#limits
- Other Copilot Studio limitations https://learn.microsoft.com/microsoft-copilot-studio/requirements-quotas

<a id="roadmap"></a>
# 🤖 Sales Order Agent Roadmap
Expand Down