Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing interacting object types, object-centric processes, leading-object executions or cross-object delay.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use the shared contract. Require the needed
advertised OCPM tools; absence stops this workflow, never falls back to case analytics.
Keep separate object context and filters:Fobj; do not copy case filterOptions.
get_ocpm_processes {} -> select returned P ->
get_process_details_v2 {processId:P} for missing metadata.
Case get_processes does not discover object-centric processes.get_ocpm_object_types {S,itemsPerPage:20,itemsToSkip:0}.
Choose returned leading type O from the user's objective; ask if ambiguous.get_ocpm_process_execution_statistics {S,leadingObjectTypeName:O,filters:Fobj}.
ProcessExecutionCount counts executions; ProcessExecutionDuration is their mean.get_ocpm_process_executions {S,leadingObjectTypeName:O,filters:Fobj,itemsPerPage:5,itemsToSkip:0},
or get_ocpm_objects {S,objectTypeName:O,filters:Fobj,itemsPerPage:5,itemsToSkip:0},
or get_ocpm_edges {S,filters:Fobj,itemsPerPage:10,itemsToSkip:0}.An exact object/execution request with cached type/scope can go directly to its drilldown; do not force a new summary. Continue needed pages or discriminating follow-ups without fixed call/row/drilldown quotas. Reuse complete results; stop when answered or no new evidence remains. No OCPM sort, generic metrics/grouping or formula-column inputs exist. Search is supported only on object types, objects and edges; aggregate statistics has no paging.
Use exact returned type names, attributes and object identifiers (objects expose Name, not invented GUIDs).
Declare leading type, propagation and date mode. For a selected-type-only timeframe:
objectTimeframeFilters:[{objectTypeName:O,startDate:START,endDate:END,
filteringType:"Contained",isInclusive:true,propagation:"SelectedObjectTypeOnly"}]
SelectedObjectTypeOnly forbids propagationDepth. RelatedObjects defaults to depth 2; depth N means N-1 relation hops. Choose explicitly when ambiguity changes scope. OCPM timeframe requires start before end and describes an exclusive end; unlike case filters, its discovered modes can include Started, Completed, Intersecting and PassThrough.
For a first-to-last path threshold with known activity values FROM/TO:
processExecutionFilters:[{leadingObjectTypeName:O,
from:{selectionType:"First",value:FROM},to:{selectionType:"Last",value:TO},
timeBetweenEventsRelation:"GreaterThan",timeBetweenEventsSeconds:SECONDS,isInclusive:true}]
Time relation and finite nonnegative seconds must be paired. Secondary object-metric Duration conditions instead use ticks; case duration filters use TimeSpan strings. Do not interchange them.
Report at most five headline rows with native units, leading type, filters and page coverage. Object-type counts are not additive unique executions. Execution Duration is not automatically the filtered path interval or invoice-to-order delay. A delay claim also needs a verified business definition/threshold. Mark unsupported interpretations inconclusive, not inferred from cases. Use the investigation method for evidence labels and compact references, counts, units, coverage and alternatives. Freeze baseline object filters separately from test filters; keep object context, leading type and propagation explicit. Stop on missing interval evidence or capability, never substitute a case-based model.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
日本語の概要は準備中です。原文の説明を表示しています。
Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings, table permissions, and web roles to `/integrate-webapi` and `/create-webroles`. Use whenever a user wants AI/Copilot output that condenses Dataverse content on a Power Pages site — an AI summary, AI-generated overview or "key insights" across a record or list, a search-results summary, a case/incident summary, or recommendation-chip refinement — even when phrased as "AI-generated paragraph", "insights", or "overview". Do NOT use for: generative pages in model-driven apps (use the model-apps `genpage` skill), Copilot Studio agents/chatbots, summarizing documents or PDFs, Power BI dashboards, plain keyword search with no AI summary, or plain Dataverse CRUD (use `/integrate-webapi`).
日本語の概要は準備中です。原文の説明を表示しています。
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
日本語の概要は準備中です。原文の説明を表示しています。
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional pages without re-creating metadata. Use when the user wants to add, connect, register, or link a Power Automate cloud flow to their site.
日本語の概要は準備中です。原文の説明を表示しています。
Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.
日本語の概要は準備中です。原文の説明を表示しています。