PMD Validations Tag Fails with Unknown Property Found Error After Switching from EL to PMD Scripting
What it means
A text area widget needs a max-length validation. The declarative validations array (the EL-based JSON syntax) is used with an expression that reaches into the widget by id and reads its value property, and Workday rejects the expression because a widget id is not a valid property path in that context.
Troubleshooting
- Confirm whether the .pmd file is using the declarative validations array (a JSON block with expression/errorMessage/onSubmitOnly) or true PMD scripting (JavaScript-like script methods). These are two different validation mechanisms and their syntax is not interchangeable.
- If the error message says Unknown Property found: value, check whether the expression references a widget id directly (e.g. txtArea.value) instead of the model field the widget is bound to. Widget ids are not addressable as JUEL properties from inside a validations expression.
- Decide whether to keep the declarative validations array (in which case the expression must reference the correct model path, not a widget id) or migrate to imperative PMD scripting, which sets and clears errors/warnings via script methods instead of a validations tag at all.
If staying with the declarative validations array, change the expression to reference the field's model path (the same binding the widget's valueOut points to) instead of the widget's id.value.
Pick one validation approach per app consistently: either the declarative validations array bound to model fields, or PMD scripting using its own error/warning-setting methods. Don't carry over widget-id-based expression patterns from EL scripting when moving to PMD scripting, since the two have different addressing rules.