[New Mission] Operative NextGen: Get started with the Hiring Agent
Summary
Author the Operative NextGen foundation mission in the current Copilot Studio experience. Learners import the existing Operative solution, seed the hiring sample data, inspect the Dataverse model, and create the Hiring Agent inside the solution.
Reuse the established Hiring Agent scenario and solution assets, but replace classic authoring paths with the modern Build, Preview, Evaluate, and Monitor experience. Duplicate checks found no issue proposing this complete Operative NextGen mission.
Proposed mission
| Field |
Value |
| Section |
Operative NextGen |
| Folder |
docs/operative-v2/01-get-started/ |
| Title |
Mission 01: Get Started with the Hiring Agent |
| Operation codename |
OPERATION TALENT SCOUT |
| Difficulty |
2 |
| Time |
45 minutes |
Scenario
Contoso needs an AI-assisted hiring system that can process resumes, match candidates, prepare interviews, and coordinate recruiters. The learner establishes the base of operations: the Operative solution, seeded hiring records, and the central Hiring Agent that later missions extend.
Use a command-center analogy: Dataverse holds the operational records, while the Hiring Agent coordinates specialized capabilities across the hiring lifecycle.
Mission objectives
- Explain the hiring automation scenario and its data relationships.
- Import and validate the Operative solution.
- Seed Job Role and Evaluation Criteria sample data.
- Create the Hiring Agent in the Operative solution.
- Validate the agent in the modern authoring experience.
Prerequisites to state in the mission
- Completion of Recruit NextGen or equivalent Copilot Studio fundamentals.
- A Copilot Studio license or trial.
- A Power Platform environment with Dataverse that permits solution import and agent creation.
- Environment Maker or equivalent permissions.
Proposed lab outline
Import and inspect the solution
Import the supplied Operative solution, publish customizations, and verify Candidate, Resume, Job Role, Evaluation Criteria, Job Application, and Hiring Hub components.
Seed sample data
Open Hiring Hub and import the supplied Job Role and Evaluation Criteria CSV files. Validate lookups, mappings, record counts, and representative records.
Create and test the Hiring Agent
Create Hiring Agent in the Operative solution with the documented description. Review the modern Build canvas, add a minimal orchestrator instruction, test a baseline conversation in Preview, and confirm the agent appears in the solution.
Acceptance criteria
- Reuse one supported Operative solution package and document its version and checksum.
- Import all required tables, relationships, app components, and dependencies without errors.
- Seed data with validated lookup mappings and expected record counts.
- Create the Hiring Agent directly in the Operative solution using the current authoring flow.
- Do not instruct learners to disable the new experience.
- Explain the modern Build, Preview, Evaluate, and Monitor surfaces without teaching later features prematurely.
- Verify the agent and Dataverse components appear in the solution.
- Capture current focused light-theme screenshots using repository standards.
- Preserve
<mission-meta /> and <analytics-tag section="operative" mission="01-get-started" />.
- Follow
WRITING_STYLE.md; run frontmatter validation, folder Markdown linting, and npm run docs:build.
Out of scope
- Detailed instructions, skills, tools, connected agents, and evaluations.
- Production data migration or environment pipelines.
- Managed-solution deployment.
- Customizing the Hiring Hub app or Dataverse schema.
Risks
- Existing solution assets may not contain every component required by the consolidated roadmap.
- CSV lookup mappings can vary by locale or environment.
- Managed-environment policy can block later workflow sharing.
- Modern solution and agent creation labels can change.
References
[New Mission] Operative NextGen: Get started with the Hiring Agent
Summary
Author the Operative NextGen foundation mission in the current Copilot Studio experience. Learners import the existing Operative solution, seed the hiring sample data, inspect the Dataverse model, and create the Hiring Agent inside the solution.
Reuse the established Hiring Agent scenario and solution assets, but replace classic authoring paths with the modern Build, Preview, Evaluate, and Monitor experience. Duplicate checks found no issue proposing this complete Operative NextGen mission.
Proposed mission
docs/operative-v2/01-get-started/OPERATION TALENT SCOUTScenario
Contoso needs an AI-assisted hiring system that can process resumes, match candidates, prepare interviews, and coordinate recruiters. The learner establishes the base of operations: the Operative solution, seeded hiring records, and the central Hiring Agent that later missions extend.
Use a command-center analogy: Dataverse holds the operational records, while the Hiring Agent coordinates specialized capabilities across the hiring lifecycle.
Mission objectives
Prerequisites to state in the mission
Proposed lab outline
Import and inspect the solution
Import the supplied Operative solution, publish customizations, and verify Candidate, Resume, Job Role, Evaluation Criteria, Job Application, and Hiring Hub components.
Seed sample data
Open Hiring Hub and import the supplied Job Role and Evaluation Criteria CSV files. Validate lookups, mappings, record counts, and representative records.
Create and test the Hiring Agent
Create
Hiring Agentin the Operative solution with the documented description. Review the modern Build canvas, add a minimal orchestrator instruction, test a baseline conversation in Preview, and confirm the agent appears in the solution.Acceptance criteria
<mission-meta />and<analytics-tag section="operative" mission="01-get-started" />.WRITING_STYLE.md; run frontmatter validation, folder Markdown linting, andnpm run docs:build.Out of scope
Risks
References