Conceptualization of Workspaces

A Workspace represents each spreadsheet where GUBUS operates. Conceptually, a workspace amalgamates all three GUBUS patterns to orchestrate your project. Consequently, a workspace comprises:

• inputs
• multipanels
• workfeeds

The most minimalistic workspace conceivable - is a solitary sheet with a workfeed on it, where (1) GUBUS posts tasks, (2) the user verifies completed tasks, and (3) GUBUS reads which tasks have been accomplished. This could serve as a production workspace for a worker at a certain stage.

The smallest independent project we can envision - a workspace with a simple one-lined multipanel and a connected workfeed that stores data. This can occur on the same sheet.

Each workspace can accommodate numerous sheets for inputs, numerous sheets for panels (although the composition of workfeed + panel is strongly recommended), and numerous sheets for transactions, storages, scanners, and so forth.

As depicted in the screenshot above, there are:

• 3 sheets for input (in combination with scanners)
• 3 sheets for workfeeds (maintaining appropriate inputs)
• 1 workfeed is united with 2 multipanels to further manage production data

In this jam production project, everything transpires in a single workspace. There are no additional tables, except for the admin table.

Project with a Single Workspace

Often in small teams and projects, all operations are consolidated into a single workspace. Numerous individuals collaborate around it - one worker maintains sheet1 under her responsibility, another maintains sheet2 under his responsibility.

Less frequently, there are multiple workspaces for inputs and for keeping manager's personal information truly private, and a few workspaces for different parts of the workflow. GUBUS is absolutely adaptable in this regard as well.

INTRODUCING THE WORKSPACES RULE

The rule screenshot above can provide significant insights about this GUBUS project:

• Observe the identical table_id value - this signifies that two workers are connected to a single workspace.
• Diverse contact data - the actions of workers are monitored individually.
• Presence of mobile contact data - this indicates that automatic mobile authorisation and mobile inputs are configured.
• Varying names - upon input, the GUBUS bot will assign them distinct names.
• Different roles - deeper within the system, there are custom workflows configured.

Projects with Multiple Workspaces

While GUBUS was initially designed for simple, single workspace projects, its first implementation was for a complex project with multiple workspaces and intricate production/sales business logic. Thus, GUBUS is well-equipped to handle such scenarios successfully!

Let's examine a production/sales/services mattress workshop project that utilizes multiple workspaces, which are divided into two categories: production workspaces and manager workspaces.

Some key points need to be clarified here:

• The 'workspaces' folder contains multiple similar workspaces for similar users - in this case, managers.
• The 'production' folder contains simple different workspaces for different production stages.
• There is undoubtedly an item mode running on GUBUS.
• There are production/storage workfeeds where items are being evaluated.
• Data in workspaces is updated as production events occur.

Illustration of a Complex Workspace

As previously mentioned, a workspace can be quite extensive and can accommodate a substantial amount of data. For instance, consider a workspace for a manager of an individual mattress workshop that manufactures 5 custom composite products and resells 50 simple products. This workspace comprises 8 sheets.

Here's what we can observe:

• 4 sheets dedicated to mosaic inputs: GASH, STOMAGASH, POMOGASH, PEREMOGASH
• 1 CORE sheet serving as the main workfeed, combined with the main directive panel - ACTIVE
• 1 sheet for storing closed items(in a workfeed) - CLOSED
• 1 sheet for recording transaction information in a workfeed - TRANSACTIONS
• 1 sheet for automating receipts - RECEIPT
• 1 sheet dedicated to client history retrieval (also a workfeed) - CLIENTS

It appears we have thoroughly explored the topic of workspaces for now. If you wish to delve deeper into the primary patterns mentioned here, such as workfeeds, mosaic inputs, or multipanels, feel free to explore them at your convenience!