Circumstance definition not taking functions
SummaryWhen attempting to save a Circumstance definition, an error is thrown: Not a valid datetime
Error MessagesNot a valid datetime
Steps to Reproduce
- Create a Circumstance template with .pxCreateDateTime
- Create a Circumstance definition and use @getCurrentDateTime() function in condition row.
- Save the rule and try to check in.
Root CauseA defect in Pegasystems’ code or rulesAs 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.
ResolutionModify the circumstance template to use "Primary.pxCreateDateTime" or "pyWorkPage.pxCreateDateTime".
Published January 30, 2017 - Updated February 11, 2017