01-31-2012 09:08 PM
<sequenceFlow id="endFlow1" sourceRef="exclusiveGw" targetRef="theEnd">
[b]<conditionExpression xsi:type="tFormalExpression">${loanRequest.approved}</conditionExpression>[/b]
Are there other xsi:type allowed? E.g. class?
And I find tFormalExpression in xsd which can be replaced by "expression".
</sequenceFlow>
<sequenceFlow id="endFlow1" sourceRef="exclusiveGw" targetRef="theEnd">
[b]<conditionExpression xsi:type="class"><extension name="com.xxx.xxxx.condition"></conditionExpression>[/b]
</sequenceFlow>
// Those two line can be noted, And we can focus on how to push process instance.
// Otherwise, we should set condition variable. Why not move those logic into other class?
// loanrequest = xxxService.find();
// runtimeService.setVariable(execution.getId(), "loanrequest", loanrequest);
runtimeService.signal(execution.getId());
02-01-2012 03:49 AM
02-01-2012 03:51 AM
02-01-2012 09:34 PM
Why would you want to do that? The tFormalExpression is a requirement of the BPMN 2.0 xsd.Now I defined a flow which all node are usertask.
02-01-2012 09:36 PM
Hi,
It's just following the BPMN specification. Yes you could implement an alternative type in the Activiti source code.
But of course you would need to change / enhance the Activiti Engine to do that.
Best regards,
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.