Did you find the solution? I can reproduce it in some components dialogs, but I cannot reproduce it in all dialogs. It's really strange

but we cannot use pathbrowser because we need to see the thumbnail image.

If you are using coral fields you can use my previous example with granite:data. I have it working in 6.3 and 6.4

You cannot block dialog's properties individually in a component You only can lock the component node

I can reproduce it in all my pathfields inside a multifield doesn`t work after update from 6.3.2.0 to 6.3.2.2 And the FP2 it was installed correctly, because we generated new servers to double check the situation.

Finally we found the solution, You can add cq-msm-lockable with granite:data/>

Actually I have the same problem with select from coral Did you find some workaround ?

I'm using classic ui to edit the model.Yes my problem is not getting the value. The problem is when I try to put the dialog value in the metadatamap Dialog Participant Step - Storing Data in the PayloadYou can store widget data in the workflow payload or in the work item metadata. The format of the name property of the widget node determines where the data is stored.Store Data with the PayloadTo store widget data as a property of the workflow payload, use the following format for the value of th...

But my problem is something different because the user need to choose between two options, and the next process step need to get this data and execute the code.Actually my problem is not get the info from working item. The problem is how can I store the info, I was checking the helpx(Creating an Adobe Experience Manager Custom Worflow Step with a dialog) but in the dialog are using ./metadata/propertywhen I use this name I have an javax.jcr.nodetype.ConstraintViolationException: No default node ...