Tines Academy › Lesson

Set the rules for each request

Add checks for missing details and possible duplicates, require manager approval for purchases of $5,000 or more, and test that the rules work together.

Objective: Define the order in which requests are checked and reviewed, and test the rules around an approval threshold.

Decide what happens to every request

Some requests need more attention before operations can review them. A requester might leave out the vendor’s website, enter an invalid email address, or ask for a vendor that’s already in the tracker. Purchases of $5,000 or more also need the requester’s manager to approve them first.

For each rule, tell Tines 3B what to check and what should happen next. For example, if the spend is $5,000 or more, send the request to the requester’s manager.

The order matters too. A request could be both a possible duplicate and over the approval threshold. Sue wants operations to check the duplicate first, so a manager doesn’t spend time reviewing a purchase that’s already been requested.

The order Sue’s rules run in

The diagram below shows how the checks work together, who reviews each request, and when operations gets notified.

Add the rules

Choose the tab that matches your setup, then send the prompt in workflow chat.

For this tracker, managers check their queue each workday rather than receiving notifications.

Add these rules in order, keeping the tracker’s existing behavior.

1. Validate the details. Require every form field. Check website and contact email formats, accepting websites with or without https://. Don’t visit websites or contact vendors. Spend must be greater than zero, with up to two decimal places. If anything is missing or invalid, say which field to fix and don’t save the request or send a notification.

2. Check for duplicates. If the website matches a saved request, save the new one as "Possible duplicate." Operations must either close it as a duplicate or clear it before the spend rule runs.

3. Route by spend. Under $5,000 goes to operations as "New;" $5,000 or more goes to the requester’s manager as "Waiting for manager." Use a manager list maintained by operations; I’ll add the real managers before going live. Managers can approve or decline, with a reason required for declines. Approval sends the request to operations for the final decision; a decline ends it. Flag requests waiting for a manager for more than 72 hours.

On the tracker’s pages, requesters can see only their own requests, and managers can see only requests awaiting their decision.

Notify operations in the confirmed test channel when each valid request is first saved, including its status. Notify them again when a manager approves it. Don't send to any other channel.

Add a manager option to the draft-only test switch and assign that test manager to the test requester. Keep the test identities blocked on live and preserve the rule that nobody can approve their own request.

Keep the workflow as a draft and summarize what changed.

Add these rules in order, keeping the tracker’s existing behavior.

1. Validate the details. Require every form field. Check website and contact email formats, accepting websites with or without https://. Don’t visit websites or contact vendors. Spend must be greater than zero, with up to two decimal places. If anything is missing or invalid, say which field to fix and don’t save the request or create a message preview.

2. Check for duplicates. If the website matches a saved request, save the new one as "Possible duplicate." Operations must either close it as a duplicate or clear it before the spend rule runs.

3. Route by spend. Under $5,000 goes to operations as "New;" $5,000 or more goes to the requester’s manager as "Waiting for manager." Use a manager list maintained by operations; I’ll add the real managers before going live. Managers can approve or decline, with a reason required for declines. Approval sends the request to operations for the final decision; a decline ends it. Flag requests waiting for a manager for more than 72 hours.

On the tracker’s pages, requesters can see only their own requests, and managers can see only requests awaiting their decision.

Once I add a connector, we want to notify operations in the confirmed test channel when each valid request is first saved, including its status, and notify them again when a manager approves it. Don't send to any other channel. For now, create a message labeled "Preview only" for operations when each valid request is first saved, including its status, and another when a manager approves it.

Add a manager option to the draft-only test switch and assign that test manager to the test requester. Keep the test identities blocked on live and preserve the rule that nobody can approve their own request.

Keep the workflow as a draft and summarize what changed.

Let Tines 3B run the tests

Read the build summary first. Check the order of the rules, how vendor websites are matched, and how the tracker finds the requester’s manager. Ask Tines 3B to explain anything unclear.

Then choose the matching tab and send the test prompt.

Test the rules on this draft as the test requester, reviewer, and manager. Check a missing required field, a repeated website, spends of $4,999.99 and $5,000.00, manager approval and decline, and a requester trying to open someone else’s request.

Use a different made-up website for each spend test, such as one.example.com and two.example.com, and start each test vendor’s name with "TEST." Check the notifications too, and only post them to the test channel.

Use separate requests for manager approval and decline. Also test an above-limit request marked as a possible duplicate: it should reach the manager only after operations clears it.

Test the 72-hour flag using a made-up request set up as waiting more than 72 hours. Don't change a real request to create this test.

For each test, show the request ID, expected result, actual result, and whether it passed, failed, or couldn't be verified. Tell me what I still need to check myself.

Test the rules on this draft as the test requester, reviewer, and manager. Check a missing required field, a repeated website, spends of $4,999.99 and $5,000.00, manager approval and decline, and a requester trying to open someone else’s request.

Use a different made-up website for each spend test, such as one.example.com and two.example.com, and start each test vendor’s name with "TEST." Check the message previews too. They should be labeled "Preview only."

Use separate requests for manager approval and decline. Also test an above-limit request marked as a possible duplicate: it should reach the manager only after operations clears it.

Test the 72-hour flag using a made-up request set up as waiting more than 72 hours. Don't change an existing request to create this test.

For each test, show the request ID, expected result, actual result, and whether it passed, failed, or couldn't be verified. Tell me what I still need to check myself.

When testing the spend rules yourself, use a different made-up vendor website for each request, such as one.example.com and two.example.com. Reusing a website would flag the request as a possible duplicate, so it wouldn’t reach the spend check until operations cleared it.

Check the results

Read Tines 3B’s test report in workflow chat.

Check the request rules

Compare the results with this table:

Test

Expected result

A required field is blank

The form explains what to fix. No request is saved and no message or preview is created.

The website is already in the tracker

The request is saved as “Possible duplicate” and waits for operations to review it.

The spend is $4,999.99

The request goes to operations as “New.”

The spend is $5,000.00

The request is saved as “Waiting for manager.”

Operations clears an above-limit duplicate

The request goes to the manager before operations can make the final decision.

A manager approves

The request goes to operations for the final decision.

A manager declines

The request ends, and the requester can see the decline reason.

A requester tries to open someone else’s request

The tracker doesn’t show the request or its details.

Check the messages

With a connector, read the messages in your test channel. Without one, check the previews.

Look for:

A message when each valid request was first saved, showing its status.

Another message when a manager approved a request.

The messages should contain the details you agreed in the previous lesson. Previews should be labeled “Preview only,” with nothing sent.

Check the waiting flag

Find the test using a request that has waited more than 72 hours for its manager.

The tracker should flag it for attention.

Try any unfinished checks

In Browser, try the page checks Tines 3B couldn’t complete. Use the test identities and made-up vendor details.

Use a different website for each spend test so the duplicate check doesn’t stop it first.

If something doesn’t match

Give Tines 3B the request ID, what you expected, and what happened. Ask for a fix that keeps the approval rules and access checks intact, then repeat the affected tests.

For a problem at the $5,000 limit, check both $4,999.99 and $5,000.00 again.

Ask it to record unfinished checks in Readme.

What to do if something still feels fuzzy

You added checks for missing or invalid details, a review for possible duplicates, and manager approval for purchases of $5,000 or more. You also checked how those rules work together, including which review happens first. Next, you’ll make sure a request stays saved even if its notification fails.

Build it safely: You compared Tines 3B’s test results with the outcomes you expected, including requests just below and exactly at the approval threshold. If a test failed, you asked for a fix that preserved the approval rules and access checks, then tested again.