I have an Activiti workflow that creates multiple (parallel) user tasks for an authorisation task (assigns each one to a group based on one element of a list).
<userTask id="authReview" name="Authorisation Review" activiti:candidateGroups="${assignee}" activiti:formKey="rowf:authReviewTask">
<documentation>
${assignee} Data Access request for approval.
</documentation>
<!-- One instance of this user task for each group that needs to authorise the request -->
<multiInstanceLoopCharacteristics isSequential="false"
activiti:collection="${rowf_reviewers}" activiti:elementVariable="assignee" >
</multiInstanceLoopCharacteristics>
</userTask>
As the ${assignee} variable is used to allocate the task to the correct group (after being read from the ${rowf_reviewers} list, is there any way to use ${assignee} to add to the task description? The task description is currently set by the documentation tag which seems to work fine but nothing is read from ${assignee}. I think this may be to do with a timing issue with the population of ${assignee} as "may" be populated before the documentation gets evaluated.
Any assistance on how to get ${assignee} into the description would be appreciated.
Solved! Go to Solution.
This appears to be a duplicate of the following Stack Exchange question i answered earlier today:
workflow - Alfresco/Activiti multi-instance task variable use - Stack Overflow
If this is a different question, please let us know.
Thanks,
Greg
This appears to be a duplicate of the following Stack Exchange question i answered earlier today:
workflow - Alfresco/Activiti multi-instance task variable use - Stack Overflow
If this is a different question, please let us know.
Thanks,
Greg
Yes, that's correct and thanks for the help. I have added information to the StackOverflow question regarding your suggested solution.
Thanks,
Stephen
Ask for and offer help to other Alfresco Process Services and Activiti Users and members of the Alfresco team.
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.