Elementary Validations
It is unequivocally apparent and utterly convenient that rudimentary data validations are inherently integrated into GUBUS and are effortlessly configurable. It poses no significant challenge to verify if a certain field is a numerical value, and another is a string value that commences with a specific character.

In the image above, you can observe that in a particular project, elementary validations such as the following are configured:
- is a number
- is a string
- is not empty
- starts with a specific character
- has a strict length
As has been reiterated numerous times, GUBUS propels a high-automation, low-click paradigm in running ERP projects. This, on the other hand, necessitates complex, double/triple layered input validations. GUBUS also accommodates such cases with the appropriate input_data_validator rule.
Robust Finances!
GUBUS has engineered a potent multi-transactional module for maintaining your finances in a straightforward, transparent, and consistently updated manner. This is where layered validations become indispensable for success.
Let's envision a scenario where your manager wishes to withdraw money from a fund with insufficient funds. This should be dynamically validated depending on the command she entered. If the validation is unsuccessful, GUBUS must provide an appropriate response to the user - hey, you are attempting to consume more than you possess...
For such purposes, GUBUS has devised a masterful hybrid pattern that combines multipanels with formulas - we refer to it as layered GUBUS validations.

The logic for two-layered validation in general terms is: IF a certain field HAS a defined value - then a second layer of validation is activated, providing a check for the associated field
The logic for the third validation layer revolves around comparing two fields with each other. It is activated with commands such as:
- not_more_than
- not_less_than
- not_before_date
- not_after_date
As expected, the result of a failed data validation is returned to the user in an appropriate form (into the bot if run from the bot, into the Google Spreadsheet workspace, if GUBUS was run from there) and further execution is halted. This is incredibly useful!
Proceed to the next chapter - Informing Teams with GUBUS patterns.
Join our Newsletter
Subscribe to stay up to date with the latest GUBUS updates, features, and videos!