StorySite — Backlog export
Every aprity scan produces a hierarchical backlog of your org as EPIC → FEATURE → USER STORY with Gherkin-style acceptance criteria. The backlog is downloadable as a multi-sheet Excel or a flat CSV, and is referred to as the StorySite export.
Unlike the Documentation Agent -- which is conversational and produces stories on demand -- the StorySite is a complete, deterministic snapshot of the whole org as a backlog, generated automatically with every scan. No prompting, no LLM credits consumed.
When to use it
The StorySite is built for one-shot deliverables, not day-to-day querying. Customers use it to :
- Plan a migration to another CRM. Hand the Excel to the receiving team -- they have every business rule as a user story with acceptance criteria, organized by EPIC (functional area) and FEATURE (theme).
- Run a refonte or platform redesign. Use the backlog as the starting point of a new project, not as a copy of the old one. Themes and acceptance criteria translate directly into your new tracker.
- Plan UAT. Every USER STORY carries a Given / When / Then acceptance criterion -- the testers know exactly what to validate.
- Onboard new team members. A consultant joining a project reads the EPICs to understand the functional scope of the org in an afternoon.
- Run an audit or compliance review. The backlog flattens every business rule with traceability back to the source artefact (object, automation, validation rule), in a format auditors recognize.
- Build a TCO or migration cost estimate. The backlog has complexity hints (T-shirt sizes) per USER STORY, which can be used to size a project in story points or in days.
If you need to ask questions or drill into a specific scenario instead, use the Documentation Agent.
Plan availability
The StorySite export is generated on every plan, including Documentation and Trial. There is no separate feature flag to turn it on for typical use.
Granularity, language, and inclusion of orphan rules can be tuned per tenant by an aprity admin -- contact support@aprity.ai if you need a non-default configuration.
What you get
Excel (.xlsx) -- 3 sheets
| Sheet | What is in it |
|---|---|
| Backlog | Every EPIC, FEATURE, and USER STORY in one flat table. Columns include the hierarchical reference (EPIC-001, FEAT-001, US-001-A), title, description, Given / When / Then acceptance criterion, complexity hint (T-shirt size), tags (theme, portability, actor, record type), and traceability columns pointing back to the source artefact. |
| Insights | Aggregate metrics for project sizing : counts per EPIC, complexity distribution, portability summary (how much of the backlog is platform-portable vs Salesforce-specific). |
| Diagrammes | Mermaid diagrams for every EPIC, rendered as embedded images. Use these in slide decks, kick-off meetings, or in a Confluence / Notion page. |
CSV (.csv)
A flat dump of the Backlog sheet only -- one row per item (EPIC, FEATURE, USER STORY), no formatting, suitable for importing into another tracker or scripting downstream transformations.
Hierarchical structure
The backlog is always a 3-level tree :
- EPIC -- a high-level functional area, e.g. "Lead-to-Opportunity conversion", "Account ownership lifecycle", "Integration with DocuSign". Typically 10–30 per org.
- FEATURE -- a coherent group of stories within an EPIC, e.g. "Validation rules on Opportunity creation", "Lead conversion automations". Typically 3–8 per EPIC.
- USER STORY -- a single, slice-able unit of business behaviour, e.g. "Block Opportunity save when Stage is Closed Won and Amount is 0". Typically 5–20 per FEATURE.
Every USER STORY references the deterministic source it was extracted from (an Apex class, a Flow, a Validation Rule, a Workflow rule, an Approval Process, …) so you can trace any line back to the org metadata.
Downloading the export
The StorySite export is available alongside your scan:
- From the Customer Portal : open the scan and use the backlog export options to download the Excel or CSV.
- Via the API : the endpoints below let you pull the same files programmatically.
| Format | Endpoint |
|---|---|
| Excel (3 sheets) | GET /v1/scans/{scanId}/story-site/export.xlsx |
| CSV (flat) | GET /v1/scans/{scanId}/story-site/export.csv |
| JSON (raw pivot) | GET /v1/scans/{scanId}/story-site |
All endpoints are HMAC-authenticated and tenant-scoped. The Excel and CSV files carry the data-classification header X-Data-Classification: CONFIDENTIAL -- treat them like the rest of your business logic, not like public content.
Configuration
The StorySite is generated automatically with every scan and is shaped by three tenant-level settings :
| Setting | Default | Meaning |
|---|---|---|
| Granularity | THEME | How many USER STORIES per FEATURE. THEME aggregates rules by theme (recommended -- typically 800–1200 stories for a medium org). RULE produces one story per rule (~2× more stories). AGGRESSIVE aggregates more (good for very large orgs). |
| Include orphan rules | true | Whether business rules not anchored in any Functional Process are still included (as their own EPIC, usually called "Other rules"). Set to false to focus only on rules covered by a process. |
| Language | en | The language of the EPIC / FEATURE / USER STORY narratives. Available on all plans: English, French, Spanish, German, Italian, Portuguese. |
Contact support@aprity.ai to adjust the granularity, orphan-rule inclusion, or output language for your tenant.
Limitations
- The StorySite reflects the last successful scan. Re-run a scan if you want the latest org state in the export.
- Mermaid diagrams in the Excel "Diagrammes" sheet are large -- the file can reach 5–20 MB for a medium org. CSV stays small.
- USER STORY titles, descriptions, and acceptance criteria are paraphrased from the source metadata. They are accurate to what was scanned, but they are not a substitute for the metadata itself (linked in every row).
- The export is not automatically pushed to Jira or Azure DevOps. To create tickets from individual stories, use the Documentation Agent and its tracker integrations (Jira, Azure DevOps), or import the CSV manually with your tracker's importer.
Troubleshooting
| Symptom | What to check |
|---|---|
| The Excel file is much bigger than expected | The "Diagrammes" sheet embeds Mermaid SVGs. Use the CSV format if you only need the flat backlog. |
| EPIC / FEATURE counts seem low | Granularity is set to AGGRESSIVE, or your scan covered a narrow scope. Adjust the scan scope or the granularity. |
| Orphan EPIC is huge | Many of your business rules are not yet anchored in a Functional Process. Either set includeOrphanRules to false, or review the Process documentation in your scan output. |
| Language of the export is wrong | Confirm the language was set correctly on your tenant. All plans accept the six languages. See Multi-language Output. |
For anything else, contact support@aprity.ai.