invalidMessage vs invalidMessageList in xCP

Basin
edited November 8, 2020 in Documentum #1
Hi. We use xCP 16.4P6 and we have remnant expressions in our project that look like this:
widgets.<widgetId>.invalidMessage

The validator does not complain and the expression has the type string, single.
However, it's not in the list of suggestions, but another one is:
  • Invalidity message (invalidMessageList)
I didn't work with xCP 2x. Does "invalidMessage" originate from there?

I also noticed that at least for text inputs the expression actually returns
{ widgetId: "<widgetId>" } 

instead of a string and this causes errors.





Tagged: