As Seen On Salesforce codeLive 📺
"Maintaining high-quality Salesforce Flows is critical for the success of your business applications. Lightning Flow Scanner is a powerful tool that can help you identify and address common issues in your Flows." - Mohith Shrivastava, Principal Developer Advocate at Salesforce.
- ✨ Count on us for Transparent, Up-to-Date Assessments of Flows, Driven by Our Commitment to Open Source.
- 🚀 Experience Empowerment at No Cost, Continuously Deepening Your Understanding of Flows.
- 💡 Drive Innovation by Integrating Low-Code and Traditional Development Workflows.
- 🤝 Empower All Voices to Shape the Standard of Flow Excellence Through Open Collaboration.
- 🌱 Promote Excellence and Reduce Technical Debt for Resilient Solutions.
Explore our Flow Analysis in Various Forms 🔍
- 💻 VSCode / Code Builder
- Analyze Flows directly within VSCode or the Salesforce Code Builder.
- 🌐 Salesforce App
- Analyze flows directly within Salesforce with our Flow Scanner App.
- 🛠️ Salesforce CLI
- Integrate Flow Analysis into Github Actions and your CI/CD pipelines.
- 🚦 Copado Pipelines
- Perform Flow Analysis as a quality gate within Copado.
Furthermore, see our:
- 📂 Demo Flows: Explore practical examples of violations and their resolutions.
- 🏛️ Forum: Ask questions and share insights on everything related to Flows.
- 💬 Chat Room: Connect & engage in real-time.
The following are the default rules included in our analysis:
| Rule | Description |
|---|---|
| Auto Layout | Elements are spaced, connected, and aligned automatically in Auto Layout Mode. |
| Copy API Name | Update API names when copying elements to maintain readability. |
| DML Statement In A Loop | Consolidate database operations to prevent exceeding governor limits. |
| Duplicate DML Operation | Prevent duplicate database operations between screens. |
| Flow Naming Convention | Establish a naming convention for better findability and consistency. |
| Hardcoded Id | Remove hardcoded ID's to eliminate data dependencies. |
| Inactive Flow | Delete unused flows to prevent unexpected behaviour. |
| Missing Flow Description | Include descriptions to document flow usage and purpose. |
| Missing Fault Path | Customize error handling with a Fault Path to handle flow failures. |
| Missing Null Handler | Validate data by checking for non-null results in Get Records operations. |
| Outdated API Version | Regularly update API versions to avoid discrepancies and ensure compatibility. |
| Process Builder | Migrate your organization's automation to Flow. |
| SOQL Query In A Loop | Consolidate SOQL queries to avoid governor limit issues. |
| Unconnected Element | Avoid unconnected elements to maintain flow efficiency. |
| Unused Variable | Remove unused variables for better flow manageability. |
Additional information on the default rules and the extensibility of the engine can be found in our Documentation.
