topic FormProperty value populated in 5.14, not in 5.16.4 in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/formproperty-value-populated-in-5-14-not-in-5-16-4/m-p/198670#M151800 <HTML><HEAD></HEAD><BODY><SPAN>We recently upgraded from Activiti 5.14 to 5.16.4. In version 5.14, formProperty tags from the BPMN of one of our extended tasks (extended via "extensionElements") had it's corresponding org.activiti.engine.form.TaskFormData object formProperty value attributes populated correctly when our FormEngine class had it's TaskFormData object injected by Activiti during workflow execution [ injected during the renderTaskForm(TaskFormData taskForm) method ]. However, in version 5.16.4, our formProperty values on the same object are no longer being populated inside of the TaskFormData.getFormProperties() list for the same workflow execution. For additional clarity, the FormProperty objects that correspond to the formProperty tags below are present within the TaskFormData.getFormProperties() list, but each of their FormProperty getValue() attributes are null. The same value attributes for the same workflow contained the correct values during v5.14 workflow execution.</SPAN><BR /><BR /><SPAN>Now in debug, I found that the following attributes in v5.16.4 of the TaskFormData object (i.e. "taskForm" below) *DO* contain the values that we used to get inside of the taskForm.formProperties list:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />taskForm.task.taskDefinition.taskFormHandler.formPropertyHandlers<EM>.variableExpression.node.child.value <BR />taskForm.task.taskDefinition.taskFormHandler.formPropertyHandlers<EM>.defaultExpression.valueExpression.node.child.value<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></EM></EM></CODE></PRE><BR /><BR /><SPAN>(both sets of formPropertyHandlers sub-attributes above have the values "jaz" and "sbLog1" in formPropertyHandlers[0] and formPropertyHandlers[1], respectively)</SPAN><BR /><BR /><SPAN>but when viewing the following in debug:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />taskForm.formProperties<EM>.value<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></EM></CODE></PRE><BR /><BR /><SPAN>the value attributes are null for the same corresponding "sbLog" and "sbLogId" formProperty elements that are present in the list.</SPAN><BR /><BR /><SPAN>Can anybody give some insight as to why the formProperty object's value attribute mapping is no longer taking place since the upgrade? I am providing the relevant BPMN. In the BPMN that you see below, we used to see the values specified in "default=${…}" being populated correctly within the value attributes of the TaskFormData.getFormProperties() list elements in v5.14. Now the same value attributes are null in v5.16.4 (but do show up the taskForm.task.taskDefinition.taskFormHandler sub-attributes noted above):</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />&nbsp;&nbsp;&nbsp; &lt;userTask id="sid value from activiti is populated correctly here" name="sb log task" activiti:candidateUsers="sbuser" activiti:formKey="sbLogTaskFormKey"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;extensionElements&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;activiti:formProperty id="sbLog" name="sbLog" type="sbString" variable="sbLog" default="${'jaz'}" writable="false" required="true"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;activiti:value id="description" name="sb log"/&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;activiti:value id="isVisible" name="true"/&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/activiti:formProperty&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;activiti:formProperty id="sbLogId" name="sbLogId" type="sbString" variable="sbLogId" default="${'sbLog1'}" writable="false" required="true"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;activiti:value id="description" name="sb log id"/&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;activiti:value id="isVisible" name="true"/&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/activiti:formProperty&gt;<BR />…<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/extensionElements&gt;<BR />&nbsp;&nbsp;&nbsp; &lt;/userTask&gt;<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>Thank you in advance for any insights.</SPAN><BR /></BODY></HTML> Wed, 26 Nov 2014 17:19:07 GMT cold_gin 2014-11-26T17:19:07Z FormProperty value populated in 5.14, not in 5.16.4 https://connect.hyland.com/t5/alfresco-archive/formproperty-value-populated-in-5-14-not-in-5-16-4/m-p/198670#M151800 We recently upgraded from Activiti 5.14 to 5.16.4. In version 5.14, formProperty tags from the BPMN of one of our extended tasks (extended via "extensionElements") had it's corresponding org.activiti.engine.form.TaskFormData object formProperty value attributes populated correctly when our FormEngin Wed, 26 Nov 2014 17:19:07 GMT https://connect.hyland.com/t5/alfresco-archive/formproperty-value-populated-in-5-14-not-in-5-16-4/m-p/198670#M151800 cold_gin 2014-11-26T17:19:07Z Re: FormProperty value populated in 5.14, not in 5.16.4 https://connect.hyland.com/t5/alfresco-archive/formproperty-value-populated-in-5-14-not-in-5-16-4/m-p/198671#M151801 <HTML><HEAD></HEAD><BODY><SPAN>Could you create a unit test showing this issue?</SPAN><BR /><BR /><SPAN>Thanks,</SPAN></BODY></HTML> Thu, 27 Nov 2014 10:42:49 GMT https://connect.hyland.com/t5/alfresco-archive/formproperty-value-populated-in-5-14-not-in-5-16-4/m-p/198671#M151801 trademak 2014-11-27T10:42:49Z Re: FormProperty value populated in 5.14, not in 5.16.4 https://connect.hyland.com/t5/alfresco-archive/formproperty-value-populated-in-5-14-not-in-5-16-4/m-p/198672#M151802 <HTML><HEAD></HEAD><BODY><SPAN>After researching, we found that a custom BPMN parse handler which was added after upgrading to v5.16 was the culprit. Sorry for any confusion.</SPAN><BR /><BR /><SPAN>Thanks</SPAN></BODY></HTML> Tue, 02 Dec 2014 20:42:59 GMT https://connect.hyland.com/t5/alfresco-archive/formproperty-value-populated-in-5-14-not-in-5-16-4/m-p/198672#M151802 cold_gin 2014-12-02T20:42:59Z