Error during testing of a case
I probably did something wrong during an earlier assignment, but every time I run a Time Off case, I get an error message saying:
- ** ** com.pega.pegarules.pub.generator.UnresolvedAssemblyError: Invalid expression or reference: line 1:6 mismatched input 'day' expecting {<EOF>, '-=', '*', '-', '<', '!=', '<=', '?', '~=', '+=', '^=', '%', '*=', '+', '<>', '=', '&&', '||', '>', '%=', '/=', '==', '/', '>='} Enter day or days of PTO leave, and hours requested each day. ^^^
I have a screenshot, but I do not know how to attach it to this item.
Pegasystems Inc.
US
That's OK, I know this error.
If you are tracking to the exercises, in the PTO Request step, you added a period in the Instructions field. I can see that in the error message.
Periods, or dots, are a reserved character in Pega 7. If you want to use this character in, say an Instruction or Audit note, then you must encase the entire sentence in double quotes.
Notice in this first example, I am not using a period, or dot.
Enter day or days of PTO leave, and hours requested each day
or, notice in this example, I am using a period (dot) so I encased the sentence in double quotes.
"Enter day or days of PTO leave, and hours requested each day."
either way will work. Make the change and you will be back on track.
eddie
Ordina
NL
Whoe! That is tricky!
I guess this needs a fix in a future release of Pega. The string entered in the instruction field should always be interpreted as a string, I guess. If it isn't unexpected behaviour like this could occur
Thanks for the quick response! I'm back on track 8-))
Han.
Pegasystems Inc.
US
>> The string entered in the instruction field should always be interpreted as a string
What if later you decide that Instruction text should captured by a Property that is populated by a rule such as a Decision Table or Decision Tree?