sf-agent-framework

workflow: id: integration-development name: Integration Development Workflow description: >- End-to-end integration development and testing workflow for connecting Salesforce with external systems. Covers design, development, testing, and deployment of integrations. type: iterative-parallel duration: 3-4 weeks per integration project_types: - api-integration - middleware-integration - batch-integration - real-time-sync - event-driven-integration sequence: # Phase 1: Integration Analysis (Days 1-3) - phase: integration_analysis duration: 3 days steps: - step: requirements_gathering agent: sf-architect participants: [sf-translator, business_stakeholders] creates: integration-requirements.md uses: integration-planning activities: business_requirements: - Data flow requirements - Business rules and transformations - Volume and frequency expectations - Error handling requirements - Performance expectations technical_requirements: - System capabilities assessment - API availability and limitations - Security requirements - Infrastructure constraints - Compliance requirements deliverables: - integration_requirements.md - data_flow_diagram.png - system_capability_matrix.xlsx - step: pattern_selection agent: sf-architect creates: integration-pattern.md uses: pattern-recommendation evaluation_criteria: - Data volume - Latency requirements - Error handling needs - System capabilities - Security constraints pattern_options: real_time: - REST API - SOAP Web Services - Platform Events - Streaming API near_real_time: - Change Data Capture - Outbound Messaging - Callouts with retry batch: - Bulk API - File-based ETL - Scheduled jobs - step: architecture_design agent: sf-integration-architect creates: integration-architecture.md uses: templates/integration-design-tmpl activities: - Design integration architecture - Define data mapping - Plan error handling - Design monitoring approach - Create sequence diagrams # Phase 2: Technical Design (Days 4-5) - phase: technical_design duration: 2 days parallel_tracks: - track: salesforce_design lead: sf-architect steps: - step: salesforce_components creates: salesforce-design.md activities: - Design Apex classes - Plan triggers/flows - Design data model changes - Plan security model - track: middleware_design lead: sf-integration-architect condition: uses_middleware steps: - step: middleware_configuration creates: middleware-design.md activities: - Design transformation logic - Plan routing rules - Design error handling - Plan monitoring - track: external_system_design lead: sf-translator steps: - step: external_system_prep creates: external-system-prep.md activities: - Coordinate with external team - Define endpoints - Plan authentication - Agree on data formats # Phase 3: Development (Days 6-15) - phase: development duration: 10 days parallel_tracks: - track: salesforce_development lead: sf-developer steps: - step: apex_development creates: apex-code/ activities: - Develop Apex classes - Create HTTP callouts - Implement error handling - Write unit tests - step: configuration agent: sf-admin creates: configuration-log.md activities: - Configure connected apps - Set up named credentials - Configure remote sites - Set up custom settings - track: middleware_development lead: sf-integration-architect condition: uses_middleware steps: - step: middleware_build creates: middleware-config/ activities: - Build transformation maps - Configure routing - Set up error queues - Configure monitoring - track: external_api_development lead: sf-developer condition: building_external_api steps: - step: api_development creates: api-specification.md activities: - Develop API endpoints - Implement authentication - Add logging - Create documentation # Phase 4: Testing (Days 16-20) - phase: testing duration: 5 days steps: - step: unit_testing agent: sf-developer creates: unit-test-results.md activities: - Test Apex classes - Test error scenarios - Validate data mapping - Check security - step: integration_testing agent: sf-qa creates: integration-test-results.md uses: integration-testing-checklist activities: - End-to-end testing - Error scenario testing - Performance testing - Security testing - step: uat_testing agent: sf-business-analyst participants: [business_users] creates: uat-results.md activities: - Business scenario testing - Data validation - Error handling verification - Performance validation # Phase 5: Deployment Preparation (Days 21-22) - phase: deployment_preparation duration: 2 days steps: - step: deployment_package agent: sf-devops-lead creates: deployment-package/ activities: - Package components - Create deployment scripts - Prepare config changes - Document deployment steps - step: production_readiness agent: sf-architect creates: readiness-checklist.md uses: deployment-readiness-checklist activities: - Review architecture - Validate security - Check performance - Verify monitoring - step: runbook_creation agent: sf-devops-lead creates: integration-runbook.md uses: templates/deployment-runbook-tmpl activities: - Document procedures - Create troubleshooting guide - Define SLAs - Plan support model # Phase 6: Deployment & Monitoring (Days 23-25) - phase: deployment_monitoring duration: 3 days steps: - step: production_deployment agent: sf-devops-lead creates: deployment-log.md activities: - Deploy to production - Validate deployment - Enable monitoring - Verify connectivity - step: smoke_testing agent: sf-qa creates: smoke-test-results.md activities: - Test connectivity - Verify data flow - Check error handling - Validate monitoring - step: hypercare agent: sf-developer duration: ongoing activities: - Monitor integration health - Address issues - Tune performance - Document lessons learned success_criteria: - All test scenarios passed - Performance SLAs met - Security requirements satisfied - Error handling working correctly - Monitoring and alerting active - Documentation complete deliverables: design: - Integration requirements - Architecture diagrams - Technical specifications - Data mapping documents development: - Apex code with tests - Configuration documentation - API specifications - Middleware configurations testing: - Test results - Performance benchmarks - Security validation operations: - Deployment package - Runbook documentation - Monitoring dashboards - Support procedures best_practices: - Always use named credentials for authentication - Implement comprehensive error handling - Log all integration transactions - Use bulk patterns for large data volumes - Monitor integration health proactively - Document all design decisions - Plan for failure scenarios - Consider governor limits in design