Support Article

Circumstance definition not taking functions



When attempting to save a Circumstance definition, an error is thrown: Not a valid datetime

Error Messages

Not a valid datetime

Steps to Reproduce

  1. Create a Circumstance template with .pxCreateDateTime
  2. Create a Circumstance definition and use @getCurrentDateTime() function in condition row.
  3. Save the rule and try to check in.

Root Cause

A defect in Pegasystems’ code or rules

As per the current implementation of circumstance definition, on save of circumstance definition, all the properties used in the definition are exposed as columns in pr_index_circumstance_def table. Column type is derived from the property type. For date/time properties, column created in this table will have DateTime as type. So, if we specify a RUF for date/time property, validation is failing because @RUFNAME(XXX) is not a valid date/time.


Modify the circumstance template to use "Primary.pxCreateDateTime" or "pyWorkPage.pxCreateDateTime".

Published January 30, 2017 - Updated February 11, 2017

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.