Try using Subform.

I have tried using subform. However that form is being used to enter data into a form grid, and it does not behave properly. The fields from the subform does not get populated back to the grid.

In the meanwhile, I am redesigning the form now and store  the values to be displayed read-only in a separate field, and use sections to hide and unhide the fields.

I have tried this method instead:Define a section where there are three fields (Value Date, Fund Type, and Quantity). I set the section attribute: Visibility to depend on another field on the screen, i.e. flag_prelocked. When launching the form, those three fields are not displayed on the screen. However when the form is submitted, their values become empty. Is this a normal behaviour, when the fields are located in a hidden section?

Thanks,

Maybe those 3 fields are empty all the while? "Field value to display this section" is left blank, perhaps it is expecting a value since you have filled up "field ID to control this section".

The fields are not empty initially. I have verified it in the table at the database itself. When I submitted the form, I checked the table at the database, all 3 fields become empty. My commonsense is that although the fields are hidden in the form, they should not be assigned empty value.

Can you provide us with minimal replicable joget app for further inspection? You can drop the .jwa file here. Thanks!

Hi Herman,

It's been 6 months, but I found it possible to make some field dynamically read-only through custom plugins by extending default WorkflowFormBinder.

I will share you the code, let's say you want to make field2 readonly, you can use:

public class MyWorkflowLoadBinder extends WorkflowFormBinder {
    @Override
    public String getName() {
        return "My Workflow Load Binder";
    }

    @Override
    public String getLabel() {
        return getName();
    }

    @Override
    public FormRowSet load(Element element, String primaryKey, FormData formData) {
        Element field = FormUtil.findElement("field2", element, formData);
        if(field != null)
            FormUtil.setReadOnlyProperty(field);
        return super.load(element, primaryKey, formData);
    }
}

The beauty is you can put this in either Forms or Sections, and I will just leave the rest to your imagination since you can almost do anything in the code 

Regards.