GUBUS RULE

GUBUS RULE is a fundamental concept in the GUBUS system. Everything in admin sheet is a RULE!

GUBUS SCHEMA is a rule. GUBUS MULTIPANEL - is a rule. GUBUS WORKFEED - is a rule. E-ve-ry-thing! Is. A rule!

Starting explanation from Object

Imagine you want to configure your cron jobs as an object:

const cron_jobs = [
  {
    job_name: "get_privat_yesterday_auto",
    job_time: "0 41 7 * * *",
    target_schema_name: "get_privat_yesterday_",
    is_active: false
  },
  {
    job_name: "get_mono_yesterday_auto", 
    job_time: "0 42 7 * * *",
    target_schema_name: "get_mono_yesterday_at",
    is_active: false
  }
];

Now, try to represent Object as Table

There is no other way, to transform object to table as:

  1. Object property names → Table header columns
  2. Array of objects → Table rows
  3. Property values → Cell values

And that is exactly what GUBUS does to Google Spreadsheets!

Visual Result: The GUBUS Rule === Object

GUBUS cron_jobs rule table example

Don’t focus on bottom row with ‘stop’ keyword in it, it is staff offering to Google Spreadsheets format, that is persisting cells formatting and data validations in case rule is empty.

💡

ONE MORE TIME! RULE IS AN OBJECT! GUBUS RULE is literally an ARRAY OF OBJECTS, represented in table format exposed to you via table.

Mandatory built-in rules that happen on each project creation:

Every GUBUS project comes with a predefined set of rules that cover all aspects of data processing and system operations. Here’s the complete list of rules and their purposes:

RULE NAME
DESCRIPTION
use_schemaV2
The heart, the core, the last stop for GUBUS. All the flows are weaved here!
route
Let the flows flow beautifully, split object avoiding filtering…
workspaces
Due to collaborative nature of GS so is User related data named in GUBUS. We know, a bit weird)
multipanel
Input data via this GUBUS pattern. Powerful, beautiful, concise
validate
Validate data either on imlicit read or on transform or even before post! Insane flexibility!
workfeed
Post data, read it, reduce, join, place under formulas - the main pattern ever!
custom_workfeed
Read same workfeed different ways for different purposes with it!
spreadsheet
Shape project structure with clever tables architecture
documents
One day there will be integration with Google Docs
mosaic
Tough GUBUS pattern to manage scattered data inputs
transform
Second main core after WORKFEED. Here man transforms and maps data. Huge functionality!
join
Data joining and relationship configuration
filter
Data filtering and selection criteria
split
Data splitting and partitioning operations
compose
Data composition and aggregation rules
compare
Data comparison and difference analysis
consume
Data consumption and processing workflows
index
Data indexing and search optimization
reduce
Data reduction and summarization operations
merge
Data merging and consolidation rules
sort
Data sorting and ordering configuration
gmail_config
Gmail integration configuration and settings
gmail
Gmail operations and email processing
turbo_sms_config
Turbo SMS service configuration
turbo_sms
SMS sending and messaging operations
bots_config
Bot configuration and setup parameters
tg_bot_menu
Telegram bot menu structure and navigation
bot_steps_config
Bot interaction steps and workflow configuration
input_bot_config
Bot input handling and validation settings
api_integration
External API integration and endpoint management
cron_jobs
Scheduled task automation and timing configuration
update_rule
Rule update mechanisms and versioning

FAQ

WHERE ARE GUBUS RULES STORED AND HOW ARE THEY ACCESSED? +

All GUBUS RULES are persisted in PostgreSQL DB to be INSTANTLY accessible during GUBUS EXECUTION. This ensures high performance and reliability when processing data flows.

HOW DO I SAVE RULE MODIFICATIONS IN GUBUS? +

For RULE to be persisted after modifications new SAVE ALL RULES GUBUS run is mandatory. There is no way to automate this flow and you have to be aware of this inconvenience. You definitely gonna turn it into habit, force to save admin each time you input changes.

HOW ARE RULES AUTOMATICALLY TRIGGERED IN GUBUS EXECUTION? +

There is no explicit READ option to involve RULE into GUBUS execution, and no need for it. If rule is mentioned in [JOIN, TRANSFORM, ROUTE or in post stage POST] it is triggered automatically.

DO AI AND ENGINE UPDATES REQUIRE MANUAL RESAVING? +

Most rules updates, provided whether by GUBUS engine or by AI development interactions doesn’t generally need to run resave. The system handles these updates automatically.

WHAT ARE THE DIFFERENT RULE READING OPTIONS? +

RULE has three read options:

  • rule_reading_off - switched not to be read
  • rule_reading_on - rule is always updated on admin save action
  • one_time_read - rule is read once, its read flag switch to rule_reading_off afterwards. Important flow for incrementors.

IS IT FORBIDDEN TO ADD CUSTOM RULES TO ADMIN? +

No, it’s not forbidden! You can add custom rules to your GUBUS admin. The system is designed to be flexible and extensible to meet your specific business needs.

CAN I CHANGE PARAMETERS OF DEFAULT RULES? +

Yes, you can modify parameters of default rules but thus you will break them! And your GUBUS will stop working!

ARE THERE OTHER RULES IN GUBUS BEYOND THE DEFAULT ONES? +

Yes! Modules like Workflow and FreeBusyDay can be injected by GUBUS in case there is need of them. These specialized rules provide additional functionality for complex scheduling and workflow management scenarios. Also, you’ll want to inject increment rules, rules to account products_ids(useful for interaction with sales sites and other api integrations), transactions_categories (mandatory classifications when you’ll built cash-flow and p&l modules)

Next Steps

Understanding GUBUS rules is fundamental to configuring your system effectively:

👉 Back to GUBUS ADMIN → - Learn about all admin areas
👉 Continue to GUBUS SCHEMA → - Learn how rules execute in data workflows