Sheet record editing

Ragic stores data in linked sheets that work like a spreadsheet backed by a database. A Beam agent reads entries across those sheets and applies the customer rule to edit fields, set a status, or add a row as information arrives. Each change is written back with a note on its source for later audit. When a rule would overwrite a field with conflicting data, touch a locked entry, or break a link between sheets, the agent pauses and asks the sheet owner to confirm, keeping structural changes with the person who designed the database.

Linked sheet references

Ragic connects sheets so a value in one can pull from or update another. A Beam agent reads related entries and applies the approved rule to populate a linked field, advance a connected record, or open the next entry in a process. Every step is logged so the chain stays clear for review. When linked sheets disagree, a referenced record is missing, or a step falls outside the mapped flow, the agent stops and routes the case to the owner, so a person resolves the reference before the process is allowed to continue.

Filtered report views

Ragic builds report views that filter and group sheet data for teams to read. A Beam agent reads the underlying entries and applies the customer rule to update a shared view, recalculate a grouped total, or note a figure that moved. The refreshed view and its numbers are logged for reference. When a total shifts beyond the agreed range, or a view draws on a sheet the rule does not cover, the agent alerts the owner with the changed entries marked, so a person checks the data before others rely on the view.