Section 16: Use in Support and Maintenance
16.1 Support use cases
- incident analysis
- log interpretation
- impact analysis
- root cause drafts
- bug triage
- troubleshooting playbooks
- user issue summaries
- knowledge article creation
- trend detection from recurring incidents
16.2 Example prompt
Analyze the following Salesforce production incident notes and logs.
Provide:
1. probable root cause
2. impacted user groups
3. immediate containment options
4. permanent fix options
5. support-friendly explanation
6. KB article draft
16.3 Support anti-patterns
- pasting raw customer PII into prompts
- using AI to communicate RCA before technical validation
- skipping incident timelines and evidence
Section 19: Prompt Library
Requirements
Act as a Salesforce business analyst.
Convert the following business requirement into epics, features, user stories, acceptance criteria, assumptions, open questions, and edge cases.
Prioritize standard Salesforce functionality.
Requirement:
[paste]
Architecture
Act as a Salesforce solution architect.
Given the requirements below, propose solution options with pros/cons, risks, scalability considerations, integration implications, and a recommended approach.
[paste]
Admin configuration
Design the Salesforce admin solution for this requirement.
Include:
- objects/fields
- validation rules
- Flow outline
- page layout or Dynamic Forms recommendations
- permission set impacts
- reporting impacts
Apex generation
Generate Apex for the following requirement using enterprise patterns:
- with sharing unless justified otherwise
- bulk-safe
- null-safe
- service layer
- test class included
- error handling included
Requirement:
[paste]
LWC generation
Create an LWC for the following use case.
Include:
- HTML
- JS
- CSS
- Apex interface assumptions
- accessibility notes
- performance considerations
- Jest tests outline
Flow design
Design a Salesforce Flow for this process.
Include:
- trigger type
- entry criteria
- decisions
- subflows
- fault paths
- naming conventions
- maintainability recommendations
Integrations
Create an integration design for Salesforce and [system].
Include:
- system of record
- API pattern
- auth model
- payload mapping
- retries
- logging
- error handling
- support ownership
Test classes
Create comprehensive Salesforce Apex tests for this class.
Cover:
- happy path
- validation failures
- limit-sensitive behavior
- bulk scenarios
- security assumptions
Test scenarios
Generate business and system test scenarios for this process.
Include:
- positive
- negative
- edge
- role-based
- integration failure
- data quality
Documentation
Turn the following implementation notes into a technical design document.
Audience: architects, developers, admins, support
Include assumptions, dependencies, design decisions, risks, and operational notes.
Release notes
Summarize these deployment changes into:
1. technical release notes
2. business release notes
3. support impact summary
4. rollback considerations
Support troubleshooting
Analyze this incident evidence and produce:
- probable root cause
- impact
- immediate workaround
- long-term fix
- required teams
- draft knowledge article
Data migration
Create a migration plan for these source datasets into Salesforce.
Include mappings, transformations, load order, validation impacts, reconciliation, and rollback considerations.
Security reviews
Review this Salesforce solution for security and compliance risks.
Consider:
- field access
- sharing
- secrets
- integration auth
- PII exposure
- auditability
- admin bypass risks
Code review
Review this Salesforce code with a senior code-review mindset.
Prioritize:
- bugs
- regressions
- bulkification
- security
- readability
- missing tests
Review this design for Salesforce performance risks.
Focus on:
- limits
- large data volume
- query selectivity
- Flow recursion
- UI performance
- integration latency
Refactoring
Refactor this Salesforce implementation for maintainability.
Keep behavior unchanged.
Improve structure, naming, reuse, error handling, and tests.
User story writing
Write a user story for Salesforce implementation using:
As a
I want
So that
Also provide acceptance criteria, dependencies, and test notes.
Acceptance criteria creation
Create detailed acceptance criteria for this Salesforce requirement.
Include business rules, permissions, edge cases, and reporting expectations.