---
title: "Comment by Maik Michel on \"Consolidating Validation Logic with APEX_ERROR\" | Hashnode"
description: "There is no disadvantage. We go some steps further and execute transactions by plsql packages which are called from a process. The processes run their own valid"
url: "https://hashnode.com/posts/validation-logic-with-apexerror/67a4c0fe879cd05d72f93e23/comment/67a527ae4dd3832d52628650"
---

[Discussion](https://hashnode.com/posts/validation-logic-with-apexerror/67a4c0fe879cd05d72f93e23)

Comment [Consolidating Validation Logic with APEX\_ERROR](https://hashnode.com/posts/validation-logic-with-apexerror/67a4c0fe879cd05d72f93e23)

[Maik Michel](https://hashnode.com/@maik-michel)

[Feb 6, 2025](https://hashnode.com/posts/validation-logic-with-apexerror/67a4c0fe879cd05d72f93e23/comment/67a527ae4dd3832d52628650)

There is no disadvantage. We go some steps further and execute transactions by plsql packages which are called from a process. The processes run their own validations and call apex\_error-api. The benefit is that all code is inside packages and therefore inside git 😉 If you define this as the way to go with your team no one is searching for missing validations inside pagebuilder.
