When you have connected an Elements space with your Salesforce Org and the Org AI Analysis feature is enabled for your space, Elements can explain not just what a metadata component does, but why it exists.
The Summary sub-tab on the Context panel explains what a component does based on its metadata definition. The Why it exists sub-tab goes further: it reads the tickets, stories, requirements, and other documentation that have been linked to the component in Elements and produces an AI-generated explanation of the business rationale behind it.
Prerequisites
Registered and verified Elements account
Connected and synced Salesforce Org
View or Edit permissions on the Org Model
Org AI Analysis feature enabled for your space (contact your Elements account manager or Elements support to enable this)
What is the context of the Why it exists tab
The tab produces an AI-generated explanation that covers:
What business changes it has supported: a summary of the work items delivered over time against this component, showing how it has evolved.
Why this component was built: the original business problem or requirement that led to its creation, based on the earliest linked tickets.
Signs of historical drift: where the linked documentation suggests that the component may have been extended beyond its original purpose, or where the original business rationale may no longer apply.
The explanation is generated by combining two inputs: the metadata definition of the component (the same source used by the Summary tab) and the linked work items (stories, requirements, and other records) that have been attached to the component in Elements.
Supported metadata types
The Why it exists tab is available for any metadata type that supports the Context panel. This includes both automation metadata and non-automation metadata.
Automation types
Apex Class
Apex Trigger
Approval Process
Aura Component
Duplicate Rule
Entitlement Process
Flow
Process
Process Builder Workflow
Lightning Component
DataRaptors
OmniScripts
Omni Integration Procedures
Global Action
Quick Action & Buttons
Restriction Rule
Validation Rule
Visualforce Component
Non-automation types
Custom Object
External Object
Custom Field
Formula Field
Tips
Link your Jira tickets and requirements to metadata components in Elements — the Why it exists tab becomes significantly more useful when there is a history of delivered work items to summarise. Even a few linked stories make a large difference.
Use Why it exists during impact assessment before making changes — understanding why a component was originally built helps you assess whether a proposed change aligns with or contradicts its original purpose.
During org cleanup or technical debt reviews, use the Why it exists tab to identify components that may have drifted from their original purpose or that no longer have a clear business rationale.
Combine with the Summary tab (what it does) and the Execution context tab (how it fits in the chain) for a complete picture: what, how, and why.