topic Historic service task name does not resolve EL expression in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/historic-service-task-name-does-not-resolve-el-expression/m-p/169974#M123307 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>You can put EL expression into user task definition. When the task is created, the expression is resolved. It's a feature of activiti. And a good feature.</SPAN><BR /><BR /><SPAN>As it turns out User tasks are different from service tasks from the historic service's point of view (and implementation point of view). Historic user tasks are stored in ACT_HI_TASKINST, service tasks and all other activities are stored in ACT_HI_ACTINST table.</SPAN><BR /><BR /><SPAN>The EL name of the User task is resolved fine in ACT_HI_TASKINST but the EL name of Service task and every other activities are not resolved in ACT_HI_ACTINST. I see that user tasks are unique from other activities from implementation point of view, but from a model perspective they are equivalent. </SPAN><BR /><SPAN>Based on what I see in org.activiti.engine.impl.bpmn.behavior.UserTaskActivitiyBehavior and ServiceTaskDelegate*ActivityBehavior</SPAN><BR /><BR /><SPAN>If I can have EL in the User Task name, why cannot I have EL in the name of a Service Task or let's say every other activities? I want the name of every activities to be presented nice and shiny not just the User task.</SPAN><BR /><BR /><SPAN>I can implement it and create a pull request. What I think we have to do:</SPAN><BR /><SPAN>In the BpmnParseHandlers e.g. in </SPAN><STRONG>AbstractBpmnParseHandler.createActivitiyOnScope()</STRONG><SPAN> change the </SPAN><BR /><PRE class="language-none line-numbers"><CODE><BR />activity.setProperty("name", flowElement.getName());<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>to:</SPAN><BR /><PRE class="language-none line-numbers"><CODE><BR />ExpressionManager expressionManager = bpmnParse.getExpressionManager();<BR />activity.setProperty("name", expressionManager.createExpression(flowElement.getName()));<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>Change the </SPAN><STRONG>DefaultHistoryManager.recordActivityStart()</STRONG><SPAN> to resolve the el expression of the activity name similar to what is found in </SPAN><STRONG>UserTaskActivityBehavior</STRONG><BR /><PRE class="language-none line-numbers"><CODE><BR />String name = (String)this.taskDefinition.getNameExpression().getValue(execution);<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; task.setName(name);<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><BR /><SPAN>Of course there might be changes needed elsewhere in the code, but I think it's a good starting point. What do you think?</SPAN><BR /><BR /></BODY></HTML> Fri, 09 May 2014 08:33:29 GMT pkonyves 2014-05-09T08:33:29Z Historic service task name does not resolve EL expression https://connect.hyland.com/t5/alfresco-archive/historic-service-task-name-does-not-resolve-el-expression/m-p/169974#M123307 Hi,You can put EL expression into user task definition. When the task is created, the expression is resolved. It's a feature of activiti. And a good feature.As it turns out User tasks are different from service tasks from the historic service's point of view (and implementation point of view). Histo Fri, 09 May 2014 08:33:29 GMT https://connect.hyland.com/t5/alfresco-archive/historic-service-task-name-does-not-resolve-el-expression/m-p/169974#M123307 pkonyves 2014-05-09T08:33:29Z Re: Historic service task name does not resolve EL expression https://connect.hyland.com/t5/alfresco-archive/historic-service-task-name-does-not-resolve-el-expression/m-p/169975#M123308 <HTML><HEAD></HEAD><BODY><SPAN>Very good point and I fully agree that we should provides this functionality across every activity type. If you can create a pull request that would be great. Please also add a couple of unit tests for this.</SPAN><BR /><SPAN>User tasks are stored in ACT_HI_TASKINST because it needs some additional columns. However, for audit log purpose etc, the user task is also part of the ACT_HI_ACTINST table just like the other activity types.</SPAN><BR /><BR /><SPAN>Best regards,</SPAN></BODY></HTML> Mon, 12 May 2014 07:17:01 GMT https://connect.hyland.com/t5/alfresco-archive/historic-service-task-name-does-not-resolve-el-expression/m-p/169975#M123308 trademak 2014-05-12T07:17:01Z