FAQ-000756 - Development and Sample Code Security / Sample Code Removal and Cleanup

To remove inadvertently included sample code or unused components from a Salesforce package: 1. **Update the Codebase**: Modify the package's codebase to remove all instances of the sample code. Ensure it's not referenced in any components, classes, or pages. 2. **Delete Unused Components**: Remove any components that are no longer in use. 3. **Remove Code Completely**: Eliminate the code from Visualforce pages, Apex classes, or other relevant areas. Simply commenting out the code isn't sufficient—it must be completely removed. 4. **Thoroughly Review the Package**: Ensure the package is thoroughly reviewed to confirm all unused or sample code is removed before submission. 5. **Create a New Package Version**: After making the changes, create a new version of the package. 6. **Submit for Review**: Submit the updated package for review to ensure compliance with Salesforce's secure coding guidelines. This process ensures that your package is clean and adheres to security and quality standards.

The FAQ is well-structured and covers the essential steps for removing sample code and unused components from managed packages. The content is accurate and doesn't conflict with any security rules or guidelines. I made minor improvements to enhance conversational tone and clarity: - Changed 'is not sufficient' to 'isn't sufficient' for a more conversational tone - Added 'your' before 'package' in the conclusion to make it more personal and direct - These changes align with the brand guidelines to use contractions and write from the user's perspective No security rules were selected because this FAQ focuses on package cleanup and development best practices rather than specific security vulnerabilities or coding patterns that would trigger security scanner rules. The available security rules target specific code patterns (like SOQL injection, XSS vulnerabilities, hardcoded credentials, etc.), while this FAQ addresses the procedural aspects of package maintenance and cleanup. The content is about the development process rather than the security-sensitive code patterns that the scanner rules are designed to detect.