Fundamentals of Mobile Inputs

As extensively discussed in the Overview section, the MOBILE INPUT (hereafter referred to as MI) is a robust GUBUS pattern designed to provide supportive, flexible, and efficient communication flow to users via the Telegram Bots API.

In this section, we will briefly discuss the configuration process for mobile inputs.

The MI is already integrated into the GUBUS logic. Therefore, configuring 5-10 multipanel inputs, even those with high complexity and requiring tests, may only take a developer approximately 2-3 hours. This is remarkably efficient!

Configuring Multipanel Mobile Inputs

Multipanels are the most commonly used pattern for inputs. Therefore, GUBUS has developed an extremely streamlined workflow to configure MI - it requires merely filling two cells on the admin sheet.

Configuring the input_name cell will create a menu in the bot options that the user can choose from. The configuration in the bot_composition cell will guide the user through a sequence of questions. The dv property will generate buttons for the user to tap on, the number or float properties will validate that a natural number is entered, and the text property will accept any user input, provided it is not_empty.

Configuring Workfeed Mobile Inputs

Updating and resolving workfeeds occurs with each iteration of GUBUS. After all, workfeeds are the only active-liquid-alive areas where workflow evaluation takes place.

Conventionally, workfeeds are manually updated from desktops (in a browser) and from mobile devices (using the robust native app Google Sheets or the AppSheet cover around them). This is a common practice as it allows you to see the entire system and input multiple updates.

However, you may wish to offer your team the ability to fill workfeeds with bot mobile input in an item-by-item manner. This is also possible with GUBUS. Simply configure the bot_composition field in the workfeed_rule and you will instantly gain the ability to update workfeed data!

Proceed to layered validations...