Record creation in custom apps

CloudTables lets a team build an application backed by a database without writing conventional code, defining tables, fields, and views for the records the app manages. A Beam agent creates a new record in one of these tables when a workflow step calls for it, such as logging a new request or an intake item, filling in the fields the app's structure requires. It reads back the created record to confirm it saved correctly. If a required field can't be determined from the available data, or the record would duplicate an existing entry, the agent routes it to a person before creating anything.

Live record updates

Because a CloudTables app updates its views as records change, a Beam agent can update a record's status or fields and have that reflected wherever the app displays it, without a separate refresh step. The agent reads the current record when a workflow condition is met, such as an approval or a status change elsewhere, and writes the update following the rule the team has approved. If the update would overwrite a change someone else just made, or the record's current state doesn't match what the workflow expected, the agent routes the conflict to a person instead of forcing the write.

Audit trail review

CloudTables keeps a history of changes made to a record, showing who changed what and when. A Beam agent reads this audit trail when a workflow needs to confirm a record's change history, such as checking whether an approval step already happened, and uses that to decide whether to proceed with the next action. When the audit trail is incomplete, shows a change that contradicts what the workflow expects, or the agent can't confirm the required step took place, it routes the record to a person to verify before acting further.