Fix CEL syntax and invalid trigger in functions-automations docs#394
Merged
Conversation
Step-output references used a nonexistent `steps.<name>.output.<field>` form; the automation CEL context is `ctx.<step_name>.<field>` per the workflow execution engine, matching expressions-workflows.mdx. Also swapped the example's "Access request created" trigger, which isn't a real automation trigger type, for "Grant found".
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
The function-editor AI entry point now opens the shared C1AI assistant rather than a dedicated copilot, and the actual button labels are "Create with Functions assistant" / "Edit with Functions assistant", not "Create with AI" / "Edit with AI".
1 task
FUNCTION_TYPE_DEFAULT isn't a real FunctionType value; the proto only defines UNSPECIFIED/ANY/CODE_MODE and explicitly calls for ANY on user functions. The Invoke example's `json` field is proto bytes, decoded by the generated gateway via plain protojson.Unmarshal, so it must be base64-encoded rather than a raw JSON string.
Training/compliance verification, custom approval routing, and risk scoring aren't good candidates today since functions can't be invoked from provisioning/access-request policies. Ticketing integration should use native connectors instead of functions. Broadened username generation into attribute generation more generally, and added out-of-band API calls as a use case.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
steps.<name>.output.<field>→ctx.<step_name>.<field>, matching the actual automation execution engine andexpressions-workflows.mdx) and swapped the example's invalid "Access request created" trigger for the real "Grant found" trigger."functionType": "FUNCTION_TYPE_DEFAULT"(not a real enum value — should beFUNCTION_TYPE_ANY) in both Create-function examples, and fixed the Invoke example'sjsonfield to be base64-encoded (it's a protobytesfield decoded via plainprotojson.Unmarshal, so a raw JSON string fails to parse).All fixes were verified against the
c1product source (protos, generated REST gateway code, and relevant Go controllers), not just re-reading the docs.Test plan