Update App Actions V3 docs with introductory explanation and diagram#236
Merged
Update App Actions V3 docs with introductory explanation and diagram#236
Conversation
…t and add visual aid
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.
Product areas affected
Documentation —
docs/API/core/app-actions-v3.mdWhat does this PR do?
Updates the App Actions V3 documentation to include a clearer introductory explanation of what App Actions do (scheduled/ad-hoc automations) and adds the "How it works" diagram, matching the explanatory style of the V1 docs.
JIRA ticket
N/A
Result
The V3 intro paragraph now explains the purpose of App Actions (running code on a schedule or on-demand for automations) rather than only describing the technical difference from V2. The existing "How it works" diagram is also included for visual context.
Checklist
Deployment instructions
No deployment instructions needed — documentation only change.
Author concerns
None.