feat: add non-triggerable sObjects reference to automation-flow-generate and platform-apex-generate skills - #346
Closed
berndmareth wants to merge 1 commit into
Conversation
…: add a list of not supported target object - reason: AI often tries to generate apex triggers or record triggered flows on not supported object
|
Thanks for the contribution! Before we can merge this, we need @Bernd-Mareth-BDS to sign the Salesforce Inc. Contributor License Agreement. |
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
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
Adds a guardrail to the automation-flow-generate and platform-apex-generate skills so they check whether a target SObject supports Record-Triggered Flows / Apex triggers before running the generation pipeline, stopping early on known-unsupported objects instead of generating metadata that will fail to deploy.
Changes
Motivation
AI generation frequently attempts to create Apex triggers or Record-Triggered Flows on objects that don't support them (setup, audit, history, and log objects), producing metadata that fails deployment. This heuristic gives both skills an early, explicit check to catch obvious cases and avoid wasted generation attempts.
Notes
The reference lists are intentionally heuristic, not exhaustive — custom objects, managed-package objects, and new/changed standard objects per release may not be covered. Both docs state this explicitly.
No functional/pipeline code changed — this is skill documentation/reference guidance only.
Reviewers may want to sanity-check the object list for accuracy (e.g. UserRole is noted as "verify per org").