Red Hat Bugzilla – Bug 1012891
Read-only does not act on some fields
Last modified: 2014-08-06 16:03:18 EDT
Clone project at https://github.com/pzapata/kie-examples.git
Start process, notice that before starting a task, you can modify the Creation Date field, even if the form is displayed in read-only mode.
All the fields need to be verified they are following the read-only flag, both set at the form level or at the field level.
Subforms are also not following that convention, if you set a subform field with readonly, it's still possible to modify the content. It should propagate the read-only behaviour to the fields inside.
It also happens with multiple subforms, it prevents the list of subitems to be displayed.
The read only property application has been reviewed.
This fix is not present in BPMS 6.0.0 ER4 - will verify it with the next release.
The problem with date inputs has been fixed. But there is still no option to show the items of multiple subform if it is marked as read-only. According to Pedro's comment (https://bugzilla.redhat.com/show_bug.cgi?id=1012891#c2) I assume it is not a feature.
Fixed disabled behaviour on subform/multiple subforms.
Commit (master): https://github.com/droolsjbpm/jbpm-form-modeler/commit/536df56ad7d53a42ccb823e66da550d6842b4908
Commit (6.0.x): https://github.com/droolsjbpm/jbpm-form-modeler/commit/079b16a17217e0abd6c1f639bc50454af68fad6b
Fixed error on HTML Labels on disabled forms.
Commit (master): https://github.com/droolsjbpm/jbpm-form-modeler/commit/6c41d28715f2f3ae3b301b45ef7b93bd32f3a1cc
Commit (6.0.x): https://github.com/droolsjbpm/jbpm-form-modeler/commit/72e4901692a0e798f5dae4ec67ec6dad15e661d9
This no longer has a target release of 6.0.0.
Verified on BPMS 6.0.1 ER1