Passing Code Expression as Parameter Value in Keyword Test

I store my different date calculations as string variables

Daily   String   aqDateTime.AddDays(aqDateTime.Today(),7)

Weekly String  aqDateTime.AddDays(aqDateTime,Today(),28)

Monthly String aqDateTime.AddMonths(aqDateTime,Today(),12) 

Then pass them in as parameters the same way 

EndDate  String  Variables.Daily

Use eval in the on screen action to get the object

MyDateField   Keys   eval(EndDate)

What data type would the 'EndDate' parameter date be in your case? I guess my programmer background wants it to by type specific but string would be fine for the purposes of populating an input field.

I'll give it a try.

It's a string too.  All strings till you need to use it and then eval(string).

I don't get the statment "store different date calculations as string variables". I've added the following parameters (first image) but would still need the nested if statements (second image) which wouldn't be a gain. What am I missing? When calling the KeyWord test the option to pass a code expression (third image) would allow for a single paramter (EndDate).

Daily and Weekly and Monthly should be project variables rather than parameters.

Then keyword test SetCycleCountingSchedule should have a parameter SetDate which is a string.

so if your subcycle was daily you might use

RunKeywordTest     SetCycleCountingSchedule  (2, Project.Variables.Daily)

and inside SetCycleCountingSchedule you will have

DateField  Keys  eval(KeywordTests.SetCycleCountingSchedule.Parameters.SetDate)

So the nested if statement would remain - not an improvement. Allowing code expressions to be passed as parameter value would remove the need for 'subcycle' and simply allow the EndData to passed to the test. Thus the feature request.

Can't you call SetCycleCountingSchedule with just one of the Daily/Weekly/Monthly parameters, then take out the nested if and just have

EndDate   Keys    eval(KeywordTests.SetCycleCountingSchedule.Parameters.EndDate)

then the daily/weekly/monthly choice gets made when you call SetCycleCountingSchedule and not inside the test itself

RunKeywordTest  SetCycleCountingSchedule (2,Project.Variables.Daily)

RunKeywordTest  SetCycleCountingSchedule (2,Project.Variables.Weekly)

RunKeywordTest  SetCycleCountingSchedule (2,Project.Variables.Monthly)

Seems wasteful to scope a global variable just to call a KeyWord test. Hence the desire to pass as a parameter as code expression..

Variables are cheap ;)

Global variables can become unmanageable if there are too many. If individual consumers of the global variables aren't aware of what others consumers are doing with the global variable it could cause problems. Scope is critical element to writing manageable code and should be as narrow as possible.