Skip to content

feat: add non-triggerable sObjects reference to automation-flow-generate and platform-apex-generate skills - #346

Closed
berndmareth wants to merge 1 commit into
forcedotcom:mainfrom
berndmareth:apex_triggers_and_flows_verify_triggerability
Closed

feat: add non-triggerable sObjects reference to automation-flow-generate and platform-apex-generate skills#346
berndmareth wants to merge 1 commit into
forcedotcom:mainfrom
berndmareth:apex_triggers_and_flows_verify_triggerability

Conversation

@berndmareth

Copy link
Copy Markdown

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

  • SKILL.md: added a "Record-Triggered flows — verify triggerability first" section instructing the pipeline to check the target object against references/non-triggerable-sobjects.md before generating, and to stop and explain if the object is unsupported.
  • non-triggerable-sobjects.md (new): reference list of common standard objects that don't support Record-Triggered Flows (e.g. -LoginHistory, SetupAuditTrail, AsyncApexJob, ApexLog, *Share/*History objects, etc.).
  • SKILL.md: added the same triggerability check to the Trigger authoring section, referencing its own references/non-triggerable-sobjects.md.
  • non-triggerable-sobjects.md (new): equivalent reference list for Apex trigger generation.

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").

…: add a list of not supported target object

- reason: AI often tries to generate apex triggers or record triggered flows on not supported object
@salesforce-cla

salesforce-cla Bot commented Sep 3, 2026

Copy link
Copy Markdown

Thanks for the contribution! Before we can merge this, we need @Bernd-Mareth-BDS to sign the Salesforce Inc. Contributor License Agreement.

@berndmareth berndmareth closed this Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants