Six Drumlin staffers might need some kind of access to the renewal flow. For each one, drag them to Owner or Run-only - based on what they actually need to do.
この演習はコースの一部です
理論を実践に変える、インタラクティブな演習のひとつをお試しください
Detect upcoming contract renewals before they lapse. Walk through the three Power Automate trigger families, pick the right one for a real-world automation problem, configure time zones so a scheduled flow fires when users expect, and add trigger conditions that stop the flow from running on weekends.
Fetch, filter, and enrich contract records using SharePoint Get items with OData queries, resolve responsible partners via Office 365 Users lookups, attach contract documents with the correct link-vs-attach security posture, draft notification emails with dynamic content, and write back an audit trail so the flow remembers what it has already done.
Route contracts by value with Condition actions and by status with Switch, guarding against type-coercion gotchas and silent Default misses. Then add run-after failure branches so one broken connector call doesn't kill the entire sweep, and close the diagnostic loop with test, run history, and Show raw outputs.
Route high-value renewals through the Approvals connector, swap binary Approve/Reject for Custom Responses, and branch on the Outcome (capital-A casing trap included). Prepare the flow for production with shared ownership, run-only access, and connection continuity, then assemble everything into a capstone pipeline.
現在の演習
