Hello, just hoping for any ideas on the best way to implement this.

Client has a bunch of manual test scripts that are run over the course of a long time; they have a value in them saying "Day 1", "Day 5" etc. Those virtual days may be a month apart or the same day. The real date values are set when the TCER are generated, and at times they may be updated (ie, all Day 10s were January 10th but halfway through testing we move them all to February 1st).

We're using RQM 5, about to be 6 in a month, solutions using v6 technology are fine.  I see there's a Manual Step custom attribute in the project config, but it doesn't seem to actually do anything or add options/new fields to each step in a manual test script. Execution variables seem to be the best idea here, though setting them uniformly is weird.  When I make a new execution variable in a test suite, then make a test case within that suite, then make a test script within that test case, I can't see any variables on the "Add execution variable" button menu in a test step.  If I run that test suite from a test plan, I can select to modify execution variable values, but the next page shows none existing.  I don't know if there would be a pro or con to making them project-level variables (they are used pretty universally, though they may have different values for different test plans).

I can add attributes to the TCERs but they aren't easily visible when running the test itself.

What I really want is to have some placeholder in test scripts, and when those scripts are run I can put a value in, ideally in bulk, and then possibly at a later time update this value for a group of selected test execution records.  It seems like execution variables are closest to this but I'm open to ideas or suggestions on how to use them effectively.