- 概要
- インストールと設定
- スタート アップ ガイド
- Delegate インターフェイス
- 最初の Delegate タスク
- Tutorial: Teach Delegate a cross-app task
- 信頼とコンプライアンス
- ガバナンス
- 機能
- Delegate for Testing
- 参照
- トラブルシューティング
- バックアップと復元
Tutorial: Teach Delegate a cross-app task
Teach Delegate a cross-app task that runs across nine systems, including legacy desktop apps, by using a project, skills, and a routine.
Teach Delegate a complex task that runs through many systems, including old desktop apps, and follows rules nobody wrote down. You set up a project, explain the systems, do the task once together with Delegate, and save the procedure as a routine that runs the task from then on.
This tutorial sets up a rebate contract across nine systems. The same steps work for any task, so swap in your own systems and rules. Use this approach when a task spans many systems and has to produce a consistent result every run. For a task in a single system or a short two-step task, a clear prompt is enough.
Example: rebate contract setup
Each time a customer signs a rebate agreement, a rebates team sets up a new rebate contract so the rebate is calculated and paid automatically every month. The example runs in a test environment with invented customers, account numbers, and contract terms.
| システム | 目的 |
|---|---|
| Malbek contracts (Google Sheet) | Queue of signed contracts: company, signed date, account number |
| Signed contracts (local folder) | The signed PDFs |
| Status list (Microsoft Lists) | Master list of rebate customers, checked for duplicates and updated with each new customer |
| Billing system (browser-based app) | The customer's billing cycle and payment days |
| Account system (browser-based app) | Where the account sits in the company structure |
| Billing Cycles and Early Pay Information (Google Sheet) | Turns billing terms into the payout schedule and rebate category |
| Rebate DB (legacy database) | Contract register, which gives the contract number that links the systems |
| PRRB (legacy database) | The rebate system that calculates and pays rebates each month |
| SAS (OneDrive) | Customer document folders, grouped by letter range |
前提条件
- Connect the apps that have a connector: Google Sheets, Google Drive, and SharePoint. In Delegate, go to Add-ons & Integrations > Connections. See Connections reference.
- Review the skills you already have. Delegate applies your existing skills in every new project and chooses them by description, so an outdated or incorrect skill can steer this task. Fix or delete those skills, or exclude existing skills when you create the project in Step 1. See Skills.
- Open the billing system and the account system in your browser, because the example has no connector for them.
Step 1: Create the project
Create a blank project for the task. The description says what the task is. It is not where you instruct Delegate. You teach the systems, steps, and working rules in conversations inside the project, so that Delegate can write them into skills and a routine.
- 新しいプロジェクトを作成します。
- For the description, enter
Rebate contract setup: setting up new customer rebate contracts for the rebates team. - On the Skills tab, review the loaded skills.
- For each skill that should not apply to this task, select Disable.
Step 2: Teach the systems
In the first conversation in the project, teach Delegate how each system works. Pick the method that suits you:
- Explain it. Best for rules and judgment a recording can't show, such as why a close name match means ask.
- Record yourself. Quickest for the clicks and order of screens. See Recording your tasks.
- Hand over existing documentation, such as a desk procedure or training guide. Written procedures may omit steps that experienced users perform from memory, so review the resulting skills carefully.
For each system, cover:
- What it's for, in one line.
- Where it is: the link, the file path, or that it's already open in the browser.
- How to look things up, for example searching billing by account number, never by name.
- Its quirks, for example that only an exact name match in the status list is a duplicate, and a close match means ask.
The message used in this example:
I work on the rebates team and set up new customer rebate contracts. Here are the systems I use and what each one is for.
- Malbek contracts (Google Sheet): our queue of signed contracts. On the TFS Entry tab, each row has the company, signed date and account number. The next contract to do is the first row not marked Entered.
<link-to-malbek-contracts-sheet>
- Signed contracts (local folder): the signed PDFs are already saved here. Find a contract's PDF by the company name. The files are named like "HARBOR POINT LOGISTICS, LLC-Tailored Fee Schedule-_Signed.pdf". Never download contracts. If one isn't in the folder, ask the user.
<path-to-signed-contracts-folder>
- Status list (Microsoft Lists): our master list of rebate customers. We check it for duplicates before setting anyone up, and add every new customer as a new row at the end. Only an exact name match is a duplicate. If something is close but not identical, ask me.
<link-to-status-list>
- Billing system (a browser-based app), already open in a browser tab: gives the customer's current billing cycle and payment days. Always search by the account number in External Customer Key, never by name.
- Account system (a browser-based app), already open in a browser tab: shows where the account sits in the company structure. Query Account # with the Customer ID from billing, and use Location Level on the account, not Account Level on the Contacts tab.
- Billing Cycles and Early Pay Information (Google Sheet): turns the billing cycle and payment days into the automation schedule and rebate category. Months in arrears is 1 under 27 payment days, 2 for 27 to 40, and 3 above 40.
<link-to-billing-cycles-sheet>
- Rebate DB (a legacy database): our contract register. Every new customer gets a contract number here, and that number links all the other systems.
<path-to-rebatedb-file>
- PRRB (a legacy database): the rebate system that calculates and pays rebates every month.
<path-to-prrb-file>
- SAS folder (OneDrive): customer document folders, grouped into letter ranges A-E, F-J, K-O, P-T and U-Z.
<link-to-sas-folder>
Turn this into a skill called Rebate systems, so you know how to use these systems next time. Keep it to the systems only: what each one is for, its address, how to look things up, and its quirks. No workflow steps or examples, since those will go into a routine later, and no instructions for working inside the two databases. It should apply whenever someone works with these systems. Say "ask the user" rather than my name. Show it to me before you save it.
I work on the rebates team and set up new customer rebate contracts. Here are the systems I use and what each one is for.
- Malbek contracts (Google Sheet): our queue of signed contracts. On the TFS Entry tab, each row has the company, signed date and account number. The next contract to do is the first row not marked Entered.
<link-to-malbek-contracts-sheet>
- Signed contracts (local folder): the signed PDFs are already saved here. Find a contract's PDF by the company name. The files are named like "HARBOR POINT LOGISTICS, LLC-Tailored Fee Schedule-_Signed.pdf". Never download contracts. If one isn't in the folder, ask the user.
<path-to-signed-contracts-folder>
- Status list (Microsoft Lists): our master list of rebate customers. We check it for duplicates before setting anyone up, and add every new customer as a new row at the end. Only an exact name match is a duplicate. If something is close but not identical, ask me.
<link-to-status-list>
- Billing system (a browser-based app), already open in a browser tab: gives the customer's current billing cycle and payment days. Always search by the account number in External Customer Key, never by name.
- Account system (a browser-based app), already open in a browser tab: shows where the account sits in the company structure. Query Account # with the Customer ID from billing, and use Location Level on the account, not Account Level on the Contacts tab.
- Billing Cycles and Early Pay Information (Google Sheet): turns the billing cycle and payment days into the automation schedule and rebate category. Months in arrears is 1 under 27 payment days, 2 for 27 to 40, and 3 above 40.
<link-to-billing-cycles-sheet>
- Rebate DB (a legacy database): our contract register. Every new customer gets a contract number here, and that number links all the other systems.
<path-to-rebatedb-file>
- PRRB (a legacy database): the rebate system that calculates and pays rebates every month.
<path-to-prrb-file>
- SAS folder (OneDrive): customer document folders, grouped into letter ranges A-E, F-J, K-O, P-T and U-Z.
<link-to-sas-folder>
Turn this into a skill called Rebate systems, so you know how to use these systems next time. Keep it to the systems only: what each one is for, its address, how to look things up, and its quirks. No workflow steps or examples, since those will go into a routine later, and no instructions for working inside the two databases. It should apply whenever someone works with these systems. Say "ask the user" rather than my name. Show it to me before you save it.
To create the skill:
- Send a message that describes the systems and asks Delegate to turn them into a skill called Rebate systems.
- When Delegate shows the draft skill, check that it:
- Covers only the systems. Workflow steps belong in the routine.
- Stays generic, with no individual customers or contracts except as examples.
- Approve the draft so that Delegate saves the skill.
Step 3: Teach the data entry
Teach what gets entered where, the same way: how the two legacy databases behave, which value goes in each field, and what goes in the new status list row.
The skill covers:
- What to watch for in the legacy databases: forms open on an existing record, dropdowns take only list values, there's no save button, and create buttons are clicked once.
- Rebate DB: click Add Contract once, then enter only the legal entity name.
- PRRB, tab by tab: every field and where its value comes from: the contract, the billing system, the account system, the Billing Cycles sheet, or a fixed team default.
- How to finish in the databases: close the form so the last edits save, then reopen it and check.
- The status list row in Microsoft Lists: what goes in each column of the new customer's row.
The message used in this example:
Let's now create a skill for entering a new customer's data in Rebate DB, PRRB and the status list.
Things to watch in the two legacy databases:
- Forms open on an existing customer's record. Before typing, check whether you're on a new record or an existing one. Never type over an existing record.
- Dropdowns: always pick a value from the list and check the value that shows. Never type free text. If the database asks whether to edit the list, answer No.
- There's no save button. A record saves when you move to another record, switch between a form and a subform, or close the form. Until then, Esc undoes the edit.
- Buttons that create records: click once and check the result before clicking again.
- On tabs that show rows, the * row is for new records. Keep each record's values on one row.
- If a validation message appears, fix the value. Don't keep dismissing it.
Rebate DB:
- Click Add Contract once. Check that a new Contract Number appeared and Legal Entity Name is empty.
- Legal Entity Name: the name from the signed contract, without periods and commas. Leave PFS Member and the other fields blank.
- Note the new contract number. It goes into PRRB and the status list.
PRRB, relationship:
- Click Add Relationship. Relationship Name: the same legal entity name. Sales Group: Client Management. Ops Manager: SAS.
- When the Reason For Changes prompt appears, enter "New contract".
- Add Relationship creates a blank contract row. Fill that one. Never click Add Contract.
PRRB, contract header:
- OLD_CONTRACT_NBR: the Rebate DB contract number.
- Status: Active.
- Executed Date: the signed date from the contract.
- Rebate Effective Date: the first day of the month after signing.
- Expire Date: three years after the effective date, at the end of the following month.
- Auto-Renewal: ticked.
PRRB, Rebate Information:
- Volume Measurement: Monthly Gallons. Billing Date Type: Cycle Close. Rebate Type: Percentage. Payout Timing: Monthly, unless the contract says otherwise. Automate Rebate: Full Automation. Payment Received: None. Automation Output: Condensed. Report Group B/I: Purchasing Account.
- Automation Schedule and Rebate Category: from the Billing Cycles sheet.
- Months in Arrears: from the payment days (1 under 27, 2 for 27 to 40, 3 above 40).
- Volume Day: the payment days from the billing system.
PRRB, Contract Conditions:
- Site Exclusions, Central Billing, Electronic Billing and International Payout %: from the contract. Leave International blank if the contract doesn't mention it.
- Max Business: 9999.
Let's now create a skill for entering a new customer's data in Rebate DB, PRRB and the status list.
Things to watch in the two legacy databases:
- Forms open on an existing customer's record. Before typing, check whether you're on a new record or an existing one. Never type over an existing record.
- Dropdowns: always pick a value from the list and check the value that shows. Never type free text. If the database asks whether to edit the list, answer No.
- There's no save button. A record saves when you move to another record, switch between a form and a subform, or close the form. Until then, Esc undoes the edit.
- Buttons that create records: click once and check the result before clicking again.
- On tabs that show rows, the * row is for new records. Keep each record's values on one row.
- If a validation message appears, fix the value. Don't keep dismissing it.
Rebate DB:
- Click Add Contract once. Check that a new Contract Number appeared and Legal Entity Name is empty.
- Legal Entity Name: the name from the signed contract, without periods and commas. Leave PFS Member and the other fields blank.
- Note the new contract number. It goes into PRRB and the status list.
PRRB, relationship:
- Click Add Relationship. Relationship Name: the same legal entity name. Sales Group: Client Management. Ops Manager: SAS.
- When the Reason For Changes prompt appears, enter "New contract".
- Add Relationship creates a blank contract row. Fill that one. Never click Add Contract.
PRRB, contract header:
- OLD_CONTRACT_NBR: the Rebate DB contract number.
- Status: Active.
- Executed Date: the signed date from the contract.
- Rebate Effective Date: the first day of the month after signing.
- Expire Date: three years after the effective date, at the end of the following month.
- Auto-Renewal: ticked.
PRRB, Rebate Information:
- Volume Measurement: Monthly Gallons. Billing Date Type: Cycle Close. Rebate Type: Percentage. Payout Timing: Monthly, unless the contract says otherwise. Automate Rebate: Full Automation. Payment Received: None. Automation Output: Condensed. Report Group B/I: Purchasing Account.
- Automation Schedule and Rebate Category: from the Billing Cycles sheet.
- Months in Arrears: from the payment days (1 under 27, 2 for 27 to 40, 3 above 40).
- Volume Day: the payment days from the billing system.
PRRB, Contract Conditions:
- Site Exclusions, Central Billing, Electronic Billing and International Payout %: from the contract. Leave International blank if the contract doesn't mention it.
- Max Business: 9999.
To create the skill:
- Send a message that asks Delegate to create a skill called Rebate data entry.
- Ask Delegate to apply the skill only when someone enters data in the two databases or the status list. Setting up a contract from start to finish is the routine's job.
- Review the draft skill.
- Approve the draft so that Delegate saves the skill.
Step 4: Do the task together once
Run the first contract step by step and check each result before Delegate moves on. This run is where gaps in the skills show up.
-
Send the following message:
Let's set up the next signed rebate contract together. Here's the flow: 1. Take the next contract from Malbek contracts and read its signed PDF. 2. Check the status list that the customer isn't already there. 3. Look up billing in the billing system and the account structure in the account system. 4. Get the schedule and category from the Billing Cycles sheet. 5. Create the contract in Rebate DB. 6. Set it up in PRRB and attach the signed PDF. 7. Create the customer's folder in SAS. 8. Add the customer as a new row in the status list. 9. Mark the contract Entered in Malbek contracts. Go one step at a time: after each step, tell me what you found or entered and wait for my OK. If I correct you, update the skill that covers it.Let's set up the next signed rebate contract together. Here's the flow: 1. Take the next contract from Malbek contracts and read its signed PDF. 2. Check the status list that the customer isn't already there. 3. Look up billing in the billing system and the account structure in the account system. 4. Get the schedule and category from the Billing Cycles sheet. 5. Create the contract in Rebate DB. 6. Set it up in PRRB and attach the signed PDF. 7. Create the customer's folder in SAS. 8. Add the customer as a new row in the status list. 9. Mark the contract Entered in Malbek contracts. Go one step at a time: after each step, tell me what you found or entered and wait for my OK. If I correct you, update the skill that covers it. -
After each step, review what Delegate reports.
-
Reply with your OK to continue. If something is wrong, send a correction instead, and Delegate updates the skill that covers it.
In the example run, two corrections went straight into the skills: read the automation schedule back after picking it from the dropdown, and which values go in each status list column.
Step 5: Save the routine
Once a run goes through cleanly, have Delegate save the flow as a routine.
-
Send the following message:
That's the whole flow. Save it as a routine called "Set up new rebate contract", with the steps in the order we just did them. For how to work in each system, refer to the Rebate systems and Rebate data entry skills instead of copying their rules into the routine. Before creating anything in Rebate DB, show me the contract terms and lookup values and wait for my OK. Add a short "How to work" section: - For each step, use a connector or API first. Switch to computer use only if there's no connector for that system, or the connector fails. - With computer use, work in the background (off screen) first. Switch to the foreground (on screen) only if the background doesn't work for that app or step. - Don't try the same step more than three times. If three attempts haven't worked, stop, tell me what you tried and what happened, and wait for my approval before trying again. Show me the routine before you save it.That's the whole flow. Save it as a routine called "Set up new rebate contract", with the steps in the order we just did them. For how to work in each system, refer to the Rebate systems and Rebate data entry skills instead of copying their rules into the routine. Before creating anything in Rebate DB, show me the contract terms and lookup values and wait for my OK. Add a short "How to work" section: - For each step, use a connector or API first. Switch to computer use only if there's no connector for that system, or the connector fails. - With computer use, work in the background (off screen) first. Switch to the foreground (on screen) only if the background doesn't work for that app or step. - Don't try the same step more than three times. If three attempts haven't worked, stop, tell me what you tried and what happened, and wait for my approval before trying again. Show me the routine before you save it. -
Review the routine.
-
Approve it.
The routine holds the steps and points to the two skills for the detail. Its one review point sits before anything is written to the databases, instead of after every step. It also carries the working rules, so they go wherever the routine goes.
Keep each piece of information in one place. Copies of the same rule in two skills, or in a skill and the routine, drift apart, and Delegate may follow the outdated one. Point from one place to the other instead.
Native Background handles web and desktop apps together without taking over your screen. Use On my screen when the background doesn't work, for example with dialogs, file pickers, or downloads. See Local security configuration.
Step 6: Run the routine on the next contract
- In a conversation in the project, start the routine in either of these ways:
/Set up new rebate contractと入力します。- Ask for the next signed rebate contract.
Delegate takes the next row in Malbek contracts, reads the contract, checks for duplicates, and looks up the customer. It then stops with the terms and values for your OK before it writes anything to the databases.
The test queue includes contracts built to stop, such as a near-duplicate and an exact duplicate. When Delegate stops on those and asks, the routine is working.