[META] Salesforce ECA 1.0.0 Roadmap

Problem/Motivation

The Salesforce ECA module has reached alpha status (1.0.0-alpha1) with core functionality for integrating Salesforce events and actions into ECA workflows. Based on analysis of real-world usage patterns, several key features are still needed to enable organizations to replace their custom event subscribers and API calls with ECA workflows.

This roadmap tracks the path to a stable 1.0.0 release.

Steps to reproduce

Not applicable for a roadmap issue.

Proposed resolution

Complete the implementation of essential Salesforce operations that will enable users to:
- Handle Salesforce errors in workflows
- Make direct API calls without custom code
- Extract field values from Salesforce records
- Check entity mapping status in conditions
- Retrieve object metadata for dynamic workflows

Remaining tasks

Phase 1: Core Components (High Priority)

- [ ] ✨ Implement Salesforce ERROR event for ECA workflows Active
- [ ] ✨ Add "Call Salesforce API" action Active
- [ ] ✨ Add "Get Salesforce Field Value" action Active

Phase 2: Helper Actions & Conditions

- [ ] ✨ Add "Entity Has Salesforce Mapping" condition Active
- [ ] ✨ Add "Entity Is Mapped to Salesforce" condition Active
- [ ] ✨ Add "Salesforce Object Metadata" action Active

Documentation & Quality

- [ ] Write comprehensive documentation with examples
- [ ] Add test coverage for new features
- [ ] Create example ECA models for common use cases

User interface changes

New events and actions will appear in the ECA configuration interface:
- Events: "Salesforce: API error occurred"
- Actions: "Call Salesforce API", "Get Salesforce field value", "Get Salesforce object metadata"
- Conditions: "Entity has Salesforce mapping", "Entity is mapped to Salesforce"

API changes

None. All additions follow existing ECA plugin patterns.

Data model changes

None. Uses existing Salesforce and ECA data structures.