The Data sources tab shows the logic behind a solution: the workflows that run its automated parts, and the functions the app uses to read and write its data.
Overview
Data sources becomes available once the solution has a workflow or an app. It has two parts, switched with the tabs at the top:
Part | What it shows | Available when |
|---|---|---|
Workflows | The automations the Solution agent built for this solution, such as sending reminders or syncing data. The tab shows how many there are. | The solution has at least one workflow. |
Functions | Functions expose the app's data operations and show how those operations are used by components. | The app has been built. Until then it shows "Available once the app is built". |
The tab opens on Workflows when the solution has any, and on Functions otherwise.
Workflows
The Workflows list shows the solution's automations with their Name, Status, Trigger, Apps Used and when they were Last Updated. You can search it, save views and reorder columns. Until the Solution agent builds a workflow, the Workflows tab stays greyed out.
Click a workflow to open it in place, without leaving the builder. You'll see the workflow's details page — including a preview of its steps — and the back button returns you to the list.
Workflows are read-only in the Solution builder. You can open a workflow in the workflow builder to inspect it, but saving and deploying are turned off there. To change a workflow, ask the Solution agent — for example "Send the reminder at 9am instead of noon." There's also no button to create a workflow here, because a workflow created outside the agent wouldn't be part of the solution.
Functions
Functions show the app's data flow in three layers: the objects that store data, the functions that read and write them, and the app's components that use those functions. Switch between two views:
Detail (the default) — a list of every function on the left. Select one to see its signature, whether it's a Query, a Mutation or both, the objects it touches, where it's Used in, and its source.
Graph — the three layers as columns joined by lines. Hover a function to trace its data flow from object to screen.
Before the app is built you'll see "No data flow yet" — "Data flow will appear once the app is built".
Testing a Function
Each function's detail has a test form. Fill in any inputs marked Required and run it to see the result as a table of records (for example "3 rows returned") or as JSON.
Note: Tests run against the app's real records using your own access. Running a function that creates, updates or deletes data really changes that data — it isn't a sandbox. Use query functions freely, and test mutations only on records you're happy to change.