This is good to know. I will make a note if users experience errors after we apply the new certificate. Thanks!

Thank you for the information. As it turns out, I was the only user with an out-of-date version of Reader.

I am also having this same issue with a form that is used in our Adobe AEM instance. Have you had any luck getting it fixed?

Here is an example where I am monitoring some date fields for changes. This code is entered as the Initialize Rule of the Root Panel object. //keep track of the initial values of the fields that you want to monitor for changes var odt = RequestDeadlineTime.value; var odd = RequestDeadlineDate.value;...

Can we expect some official communications on how to mitigate this any time soon?

I was able to set some variables for the original values in the guide panel init that persisted when the event fired. This works great, thanks!

payload.oldText returns 'undefined' for every change. I was trying to avoid using hidden fields, but I guess I don't have much of a choice. 

Hello, Is there a way to determine if the value of a field has been changed in an adaptive HTML form other than having a hidden field with the initial value in it that gets compared when the Value Commit event is triggered?

In case anyone wants to know what happened here, this is the error message you receive when you have an adaptive form that uses an xsd schema and you add an unbound control to the form. You can either live with the error message, or bind it to an element in your schema.

I added the form to a different server and also added the relevant processes to workbench. When I render the form in the Workspace UI on this new server, I am still getting these error messages.