sf-agent-framework

workflow: id: release-deployment name: Release Deployment Workflow description: >- Complete release management and deployment orchestration for Salesforce implementations. Manages the end-to-end process from final testing through production deployment and hypercare. type: gated-sequential duration: 5-7 days project_types: - major-release - minor-release - hotfix - emergency-patch sequence: # Phase 1: Pre-Release Validation (T-5 days) - phase: pre_release_validation timing: T-5 days steps: - step: code_freeze agent: sf-developer participants: all_developers creates: release-candidate.md activities: - Merge all feature branches - Create release branch - Tag release candidate - Generate release notes - Lock development branches validations: - All PRs merged or deferred - No critical bugs open - Code coverage >85% - Static analysis passed - Security scan clean deliverables: - release_candidate_tag - release_notes_draft.md - deferred_items.xlsx - step: final_testing agent: sf-qa participants: [sf-developer, business_users] creates: final-test-report.md uses: release-readiness-checklist test_types: regression_testing: duration: 2 days coverage: 100% critical paths tools: [Selenium, Provar] integration_testing: systems: [ERP, Marketing, Analytics] scenarios: End-to-end flows data: Production-like volumes performance_testing: load: 2x expected peak response_time: <3 seconds concurrent_users: 500 gate_criteria: - Zero critical defects - Less than 5 major defects - Performance SLAs met - Integration tests passed - step: security_validation agent: sf-security-architect creates: security-clearance.md uses: security-scan-checklist activities: - Run security scanning tools - Review CRUD/FLS settings - Validate sharing rules - Check encryption status - Verify compliance requirements deliverables: - security_scan_report.pdf - compliance_checklist.xlsx - risk_assessment.md # Phase 2: Deployment Preparation (T-3 days) - phase: deployment_preparation timing: T-3 days steps: - step: deployment_package_creation agent: sf-devops-lead creates: deployment-package/ uses: deployment-checklist activities: - Create change sets/packages - Validate in staging - Document manual steps - Prepare data scripts - Package configurations components: - Apex classes and triggers - Lightning components - Flows and processes - Custom objects and fields - Profiles and permission sets - Email templates - Reports and dashboards - step: deployment_validation agent: sf-release-manager creates: validation-report.md activities: - Validate package in Full sandbox - Run all tests - Check code coverage - Verify configurations - Test rollback procedure success_criteria: - All components deployed successfully - All tests passed - No deployment errors - Rollback tested successfully - step: communication_preparation agent: sf-orchestrator creates: communication-plan.md activities: - Prepare stakeholder notifications - Create user communications - Schedule deployment window - Prepare support documentation - Plan hypercare coverage deliverables: - stakeholder_email.html - user_notification.html - deployment_schedule.xlsx - support_contacts.md # Phase 3: Production Deployment (T-1 day) - phase: production_deployment timing: T-1 day steps: - step: pre_deployment_checkpoint agent: sf-release-manager participants: [sf-orchestrator, sf-architect, sf-devops-lead] creates: go-no-go-decision.md activities: - Review deployment checklist - Confirm all approvals - Verify backup completed - Check system health - Final go/no-go decision gate_criteria: - All tests passed - Approvals received - Backup confirmed - No blocking issues - step: production_backup agent: sf-admin creates: backup-confirmation.md activities: - Full metadata backup - Data export of critical objects - Document current state - Store backup securely - Verify restoration procedure - step: deployment_execution agent: sf-devops-lead participants: [sf-developer, sf-admin] creates: deployment-log.md activities: - Deploy to production - Execute manual steps - Run data scripts - Validate deployment - Enable new features monitoring: - Real-time deployment tracking - Error monitoring - Performance monitoring - User activity tracking - step: post_deployment_validation agent: sf-qa creates: validation-results.md activities: - Smoke testing - Critical flow validation - Integration verification - Performance check - Security validation duration: 2-4 hours # Phase 4: Go-Live Activities (T-0) - phase: go_live timing: T-0 (Launch day) steps: - step: feature_enablement agent: sf-admin creates: enablement-log.md activities: - Enable new features for users - Update page layouts - Activate flows/processes - Enable integrations - Update permissions - step: user_communication agent: sf-orchestrator activities: - Send go-live announcement - Share training resources - Communicate support channels - Publish release notes - Update documentation portal - step: monitoring_activation agent: sf-devops-lead creates: monitoring-dashboard.md activities: - Enable production monitoring - Set up alerts - Configure dashboards - Start logging - Track KPIs # Phase 5: Hypercare (T+1 to T+5) - phase: hypercare timing: T+1 to T+5 days steps: - step: enhanced_support agent: sf-orchestrator participants: [sf-developer, sf-admin, sf-qa] duration: 5 days activities: daily_standup: - Review overnight issues - Prioritize fixes - Assign resources - Update stakeholders issue_tracking: - Log all issues - Categorize by severity - Track resolution time - Document workarounds performance_monitoring: - Track response times - Monitor error rates - Check resource usage - Validate SLAs - step: issue_resolution agent: sf-developer participants: [sf-admin] activities: - Fix critical issues immediately - Deploy hotfixes if needed - Update configurations - Optimize performance - Document solutions - step: user_feedback agent: sf-business-analyst creates: feedback-summary.md activities: - Collect user feedback - Identify training gaps - Document enhancement requests - Measure adoption rates - Update FAQs - step: stabilization_review agent: sf-release-manager timing: T+5 days creates: stabilization-report.md activities: - Review all issues - Assess system stability - Document lessons learned - Plan improvements - Close hypercare phase success_criteria: deployment: - Zero deployment failures - All components activated - No data loss - Rollback not required quality: - Critical defects: 0 - Major defects: <5 - Performance SLAs met adoption: - User login rate >90% - Support tickets <expected - Positive feedback >80% rollback_procedure: triggers: - Critical functionality broken - Data corruption detected - Performance degradation >50% - Security vulnerability exposed steps: - Stop all user access - Restore from backup - Revert configurations - Validate restoration - Communicate status - Investigate root cause deliverables: pre_deployment: - Release notes - Test results - Security clearance - Deployment package deployment: - Deployment log - Validation results - Go-live confirmation post_deployment: - Hypercare reports - Issue log - Feedback summary - Lessons learned