Skip to content

Document app custom operations in Business Applications reference - #232

Closed
Javad Zarrinabadi (v-jazarr) wants to merge 1 commit into
microsoft:mainfrom
v-jazarr:u/jazarr/app-custom-operations
Closed

Javad Zarrinabadi (v-jazarr) wants to merge 1 commit into
microsoft:mainfrom
v-jazarr:u/jazarr/app-custom-operations

Conversation

@v-jazarr

@v-jazarr Javad Zarrinabadi (v-jazarr) commented Oct 19, 2026 •

Copy link
Copy Markdown

Summary

Documents app custom operations in the Business Applications reference for the workiq skill.

Apps can expose custom operations directly under the app at
/businessapps/environments/{environmentId}/apps/{appName}/operations/{operationName}. The reference didn't cover this path before, so agents had no guidance for finding or calling these operations.

Changes

  • Operation table: adds two rows.
    • List an app's custom operations: get_schema on the app path /businessapps/environments/{environmentId}/apps/{appName}; its app-level operations are the app's custom operations.
    • Invoke an app custom operation: get_schema, then do_action on the exact .../apps/{appName}/operations/{operationName} path, with the operation's inputs in jsonBody.
  • App-scoped paths section: describes app operations at two levels:
    • Table-level built-in record operations at .../apps/{appName}/tables/{tableName}/operations/{operationName}.
    • App-level custom operations at .../apps/{appName}/operations/{operationName}, listed by get_schema on the app path.

This is a documentation-only change to plugins/workiq/skills/workiq/references/business-applications.md. The wording matches the final version of the same fix in bic/BusinessAppsCoworkPlugin#24. The branch is rebased on the latest main, and the tests/workiq-guidance suite passes (348/348).

Eval evidence

We ran an A/B eval on the prod ring through Cowork, comparing the BusinessAppsCoworkPlugin skill with and without this wording. The workiq skill itself was not evaluated directly; the evidence comes from the same text in the Cowork plugin.

Suite Before After
App custom operations (11 prompts × 3 runs) 26/33 33/33
Golden regression subset (14 prompts × 3 runs) 18/42 16/42 (parity; the differences are judge variance on identical tool calls)
Avg credits per run (targeted / golden) 26.8 / 35.2 26.7 / 35.8

Without the guidance, the agent rarely found mutating app operations such as flag_project_at_risk (1 of 6 runs). With it, every app-operation prompt passed, at no extra cost.

Discovery (business-applications.md): list an app's custom operations with
get_schema on the app path, and note that app operations exist at table level
(.../apps/{appName}/tables/{tableName}) and app level
(.../apps/{appName}/operations/).

Actions (business-applications-actions.md): split the app operation row into
table-level record operations and app custom operations invoked with do_action
on the exact .../apps/{appName}/operations/{operationName} path, inputs in
jsonBody.

Mirrors BusinessAppsCoworkPlugin PR microsoft#24.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@v-jazarr

Copy link
Copy Markdown
Author

Closing this PR. Per the Work IQ contribution workflow, changes to features already public in production now land first in the internal workiq-preview plugin, run through Work IQ evaluations, and reach this repository through the stable promotion.

The same change, already rebased onto the 3.0.0 split of business-applications.md and business-applications-actions.md, is now ADO work-iq-skills PR 25191 (internal): https://microsoftgraph.visualstudio.com/Graph%20Developer%20Experiences/_git/work-iq-skills/pullrequest/25191

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant