Skip to content

Greenlight developer reference

Build commands around reviewed eligibility checks before starting an approval. Start and Decide are writes with identity and process rules. Never manufacture approval assignments or decisions by directly updating their tables.

Reads available processes and locked columns for an accessible business record. The caller must be able to read that record. The empty arrays illustrate no eligible process or lock.

Transport: unbound Dataverse action; JSON string Request in, JSON string Response out. pfx_ is a prefix token, not a literal deployment name. Read the calling conventions first.

Inner Request — illustrative
{
"table": "account",
"recordId": "11111111-1111-1111-1111-111111111111"
}

table: required logical table name. recordId: required GUID. available contains eligible process choices; locked contains logical column names.

Inner Response — illustrative
{
"administrator": false,
"available": [],
"locked": []
}

The schema does not declare an execute privilege for this operation; runtime checks still apply. Prefix tokens in table names resolve with the installed publisher. Record access, module role checks and input validation can further restrict the call. Do not interpret a missing execute privilege as anonymous or unrestricted access.

Handle a Dataverse fault separately from validation findings in the response. Test invalid input and the intended non-administrator role. Do not treat an empty result as a grant of access or a guarantee that no configuration exists.

Selected schema-declared registrations are shown for troubleshooting context. This is not a complete installed registration inventory. Preserve module-owned registrations; do not duplicate or disable them.

Owned registration Message / table Declared stage / mode
Greenlight: protect process create Create · pfx_approvalprocess PreOperation / Sync
Greenlight: protect process update Update · pfx_approvalprocess PreOperation / Sync
Greenlight: protect process delete Delete · pfx_approvalprocess PreOperation / Sync

The full execution path may also include dynamically maintained registrations. Inspect the installed solution for exact stage, mode, filters and images before investigating interactions with your own plugins.

Confirm the installed operation name and permissions. Test representative data, empty results and denied access. Keep your integration in its own solution, and review contract changes before upgrading.

Administrator guide · Extension boundaries