Module-code verification layer to automatically validate user input

A back-end computer system for validating module codes, the back-end computer system being communicatively connected to a front-end system that is configured to execute UI elements, the system comprising:

• a processor configured with a module code verification layer module, wherein the module code verification layer module is adapted to respond to receiving a module code associated with a UI element by:
• retrieving, via the network, a technical name of a UI screen associated with a process from a kernel of an operating system executing on the front-end computer system;
• determining if the UI screen exist;
• if the UI screen does not exist, reporting that the module code verification layer module corresponding to the module code will not be executed, and ending the method;
• if the UI screen exists, retrieving, via the network, a status of the UI element stored in a UI status table at the front-end computer system;
• verifying whether the module code is valid for the UI screen based on the status, the verifying includes verifying whether the UI screen is enabled;
• and
• if the module code is valid and the UI screen is enabled, executing a module corresponding to the module code;
• otherwise reporting the module is not valid and the UI screen is not enabled.

A machine-readable non-transitory medium having stored thereon machine-executable codes that, when executed, performs a method executing UI elements on a front-end computer system by validating module codes associated with the UI elements on a back-end computer system, wherein the front-end computer system is connected to the back-end computer system via a network, the method comprising:

• responsive to receiving a module code associated with a UI element on the back-end computer system from one of a plurality of processes executing on the front-end computer system, wherein the module code is associated with the UI element by retrieving a technical name of a UI screen associated with the one process from a kernel of an operating system executing on the front-end computer system:
• determining if the UI screen exist;
• if the UI screen does not exist, reporting that the module corresponding to the module code will not be executed, and ending the method;
• if the UI screen exists, retrieving, via the network, a status of the UI element stored in a UI status table at the front-end computer system;
• verifying whether the module code is valid for the UI screen based on the status, the verifying includes verifying whether the UI screen is enabled;
• and
• if the module code is valid and the UI screen is enabled, executing a module corresponding to the module code;
• otherwise reporting that the module is not valid and the UI screen is not enabled.