Step 5: Explore the Data Layer — PlanX Digital Planning Walkthrough
Open the Hasura console to browse tables and explore the GraphQL API
Great! You've deployed the demo
Now let's walk through what you just deployed and see it in action.
Start WalkthroughChoose your next step
Generate Evidence Pack
Create your business case documentation with what you've learned.
Generate Evidence PackWalkthrough progress
Step 5 of 5 • 2 minutes
Explore the Data Layer
Open the Hasura GraphQL console to see how PlanX stores flow data, and run a sample query.
Screenshot updating - please check back soon
Screenshot updating - please check back soon
Expected outcome
- Hasura console opens and shows the PlanX database tables
- You can browse the flows, teams, and sessions tables
- GraphiQL interface is available to run GraphQL queries
Access the Hasura console
-
Find the Hasura credentials
Go back to the CloudFormation console (opens in new tab) and find these outputs:
HasuraConsoleUrl— the Hasura console URLHasuraAdminSecretOutput— the admin secret for authentication
-
Open the Hasura console
Open the
HasuraConsoleUrlin a new tab. When prompted for the admin secret, enter the value fromHasuraAdminSecretOutput. -
Browse the database tables
Click the Data tab in the Hasura console to see the PlanX database schema. Key tables include:
Table What it stores flowsPlanning application flow definitions (the node graphs you edited) teamsCouncil teams and their settings usersEditor users and their team memberships sessionsApplicant sessions (data collected during a flow) published_flowsPublished versions of flows available to applicants -
Try the GraphQL API
Click the API tab to open GraphiQL. Try a simple query to list the flows:
{ flows { id slug team { name } updated_at } }Click the play button to run the query. You'll see the flows you browsed in Step 2, now as structured GraphQL data.
-
Understand the architecture
Hasura sits between the PlanX application and the Aurora PostgreSQL database. It provides:
- GraphQL API — used by the React editor and the applicant-facing frontend
- Real-time subscriptions — for collaborative editing via ShareDB
- Role-based access control — different permissions for editors, admins, and public access