Etendo Dev Assistant — Shared Guidelines

Etendo ERP development best practices include using subagents for Gradle task execution, managing Java environment setup, and following strict naming conventions for database artifacts to ensure robust builds.

To execute SQL within Docker for Etendo ERP, follow standardized guidelines that define safe database interaction methods, ensuring operations adhere to the platform's specific containerized environment requirements.

Yes, Etendo development supports webhook and headless endpoint integration, providing standardized operational guidelines to interact consistently with the backend and prevent common connection errors.

Validating Application Dictionary changes and sorting sourcedata XML in Etendo requires following specific AD validation checks and XML editing procedures to prevent errors and maintain data integrity.

The recommended Git workflow and SonarQube analysis process for Etendo modules involves applying clear rules for version control and code quality analysis to streamline development and improve maintainability.

Etendo Gradle builds often fail due to Java version mismanagement or incorrect context detection; avoiding these pitfalls requires adhering to established error prevention guidelines for database operations and AD changes.