topic formProperty with default value saved to the database even though writable='false' in Alfresco Archive

formProperty with default value saved to the database even though writable='false'

alexg — Wed, 23 Oct 2013 22:28:04 GMT

Hi all,In my bpmn file I have a "status" formProperty declared as follows:<userTask id="handleRequest" name="Handle request"> <extensionElements> <activiti:formProperty id="requestApproved" name="Do you approve this request" type="enum" required="true"> <a

Re: formProperty with default value saved to the database even though writable='false'

martin_grofcik — Thu, 24 Oct 2013 21:58:47 GMT

Hi Alex.

I tried to debug it too. Values are stored in the database when there is
org.activiti.engine.form.FormProperty#isWritable
set to false.
java docs says:
/** Is this property expected when a user submits the form? */

I used this jUnit test in 5.14

org.activiti.engine.test.api.form.FormServiceTest#testFormPropertyHandling


    try {
      properties = new HashMap<String, String>();
      properties.put("speaker", "its not allowed to update speaker!");
      formService.submitTaskFormData(taskId, properties);
      fail("expected exception about a non writable form property 'speaker'");
    } catch (ActivitiException e) {
      // OK
    }

where speaker is read only. This test passed. Speaker variable was set at formService.submitStartFormData(procDefId, properties)

I did not find test for default value.

Re: formProperty with default value saved to the database even though writable='false'

alexg — Sat, 26 Oct 2013 02:29:23 GMT

Thank you, Martin. I should have provided the unit test for this to make the matter clear. What I mean is slightly different from what the above-mentioned code tests. I've attached the patch with the unit test and corresponding bpmn. The unit test fails exactly where I expect it to fail. The form property in question is "status" declared in "handleRequest" user task. Hope it helps.