Tines Academy › Lesson
Brief it and build it
Give Tines 3B a brief for Sue’s finished tracker, then ask it to add a review step for operations.
Objective: Describe a complete workflow in a brief, ask Tines 3B to build one stage, and check that it follows your instructions.
Describe the whole process, then build one stage
You’ve built the request page and list. Now you’ll give Tines 3B the full brief and ask it to build the review step.
A brief is a prompt that describes the whole workflow you want to build. Sue’s finished tracker will check requests, flag possible duplicates, send larger purchases to a manager, and let operations know when something needs attention. You won’t build all of that in this lesson. Giving Tines 3B the full picture helps it make changes with the later stages in mind, while working through one stage at a time gives you less to check before moving on.
Before you build the review step, decide who needs to see which request details, like names, email addresses, and purchase amounts, and who can approve or decline a request.
Those rules control what people can see and do on the tracker’s pages. You’ll give requesters, reviewers, and managers different views of the tracker. But remember: anyone who can open the workflow itself can also look through its storage, so only give that access to people you trust with all the requests.
Add a review step for operations
Open the tracker you built in the previous lesson and send this prompt in workflow chat. The prompt asks Tines 3B to add a test switch, which lets you try the tracker as a requester and a reviewer without asking someone else for help.
You’ll use Sue’s example approval rules and a test reviewer for now.
Later, the tracker will check for missing details, flag repeat vendor websites, send requests of $5,000 or more to a manager first, and notify operations about new requests. It must never contact vendors.
For now, add only the operations review step and a draft-only test switch. On the tracker’s pages, requesters can see only their own requests. Operations reviewers can see all requests. Only operations reviewers can approve or decline requests, declines need a reason, and nobody can approve their own request. I’ll add the real reviewers before going live.
The test switch should let me act as:
- A requester using my signed-in identity, so I can see requests I’ve already submitted.
- A different person who is an operations reviewer and can submit requests and review other people’s requests, but can’t approve their own.
Keep my existing request assigned to my signed-in identity. Make sure the two sample requests belong to fictional people other than the test reviewer, so the reviewer can act on them.
Label the switch "Test only." Hide it on live and prevent the test identities from being used there, even without the switch.
Keep the workflow as a draft. Summarize what changed, how the tracker checks who can view or decide on a request, and anything you couldn't verify.
Check what Tines 3B built
Use the test switch for these checks. Before team use, you’ll still need to check access with another person’s account but for now, ask Tines 3B to record “Access not tested with a second person” in Readme.
Review the build summary
Read the summary in workflow chat. Look for how the tracker identifies reviewers and checks who can approve or decline a request.
The changes should cover the review step and test switch only. Manager approval, duplicate checks, and notifications come later.
Try the requester’s view
Open the list in Browser and use the test switch to act as a requester.
You should see your own request, but no other people’s requests or buttons to approve or decline.
Approve a sample request
Switch to the test reviewer and approve one of the sample requests.
Its status should change from “New” to “Approved.”
Try declining without a reason
Stay in reviewer mode. Find the request you submitted in the previous lesson and try to decline it without entering a reason.
The tracker should ask for a reason and leave the status as “New.”
Add a made-up reason and decline the request. Its status should change to “Declined.”
Check what the requester sees
Switch back to requester.
Open your declined request. You should see its status and the reason the reviewer entered.
Try approving your own request
Switch to reviewer again and submit a new request.
While still acting as that reviewer, check that you can’t approve the request you just submitted. Its status should stay “New.”
Switch back to requester when you’ve finished.
If something doesn’t match
Tell Tines 3B which test identity you used, what you tried, and what happened. Ask for a focused fix, then repeat the affected check.
Use a new made-up request if you need to repeat an approval or decline test. Ask Tines 3B to record unfinished checks in Readme.
If the summary includes something you didn’t ask for, ask Tines 3B what it does. Keep this stage focused on the review step; you’ll add notifications and other rules later.
What to do if something still feels fuzzy
You described Sue’s finished tracker to Tines 3B, then asked it to add the review step. You tested how operations approves and declines requests, and what requesters can see afterward. Next, you’ll add a notification so Sue’s team knows when a new request needs review.
Build it safely: You used the test switch to check what requesters and reviewers could see and do. You also learned why access to the workflow itself should stay with people who can be trusted with all its saved requests.