Parameter Rules on effective date

Chad Dirst

We would like to write a "confirmation required" parameter rule on various actions that validate the date entered is current (i.e. isn't more than 240 days in the past).

We are able to write various parameter rules against other fields, however, the effective date field is troublesome for us and I'm not sure if its due to a syntax error I am making or a limitation.

Has anyone been able to successfully write parameter rules on the effective date field?

Below are just a few of my many attempts to get this to work.  

Employee_effective_date

    if (Employee_effective_date < (system current date - 240 days))
        confirmation required
            "Warning!StartDateIsMoreThan8InThePastContinueYes?"

-------------------------------------------------------------------------------------------------------------

effective date

    if (effective date < (system current date - 240 days))
        confirmation required
            "Warning!StartDateIsMoreThan8InThePastContinueYes?"

Thank you.

SQL DB guideline.xlsx

Chad Dirst

Support was able to inform me the effective date is a special framework field and because its not defined as a parameter on an action request it cannot have parameter rules identified under it.  However, you are able to write a parameter rule using the effective date if you put it under a different heading (that is defined as a valid parameter for the action request in question.

For example, this would be valid

HROrganization

    if (effective date < (system current date - 240 days))
        confirmation required
            "Warning!StartDateIsMoreThan8InThePastContinueYes?"