cancel
Showing results for 
Search instead for 
Did you mean: 

Task Id not editable

tvanhoec
Champ in-the-making
Champ in-the-making
Hi,

When using the designer the Id for a task is not editable; the API however queries always on this Id.

ex:
Execution currentWaitExecution = runtimeService.createExecutionQuery().processInstanceId(processInstanceId).activityId("receivetask3").singleResult();

As you can see this results in unreadable code (servicetaks3 doesn't ring a bell). Maybe a candidate for improvement?

Kind Regards,
Tom
7 REPLIES 7

tiesebarrell
Champ in-the-making
Champ in-the-making
Tom,

yes, this could be an improvement, although we would need to ensure the validation of the process trips if you manually define an id that already exists. Could you create a Jira issue for this please?

tvanhoec
Champ in-the-making
Champ in-the-making
ACT-678Activiti designer - Task Id not editable

tiesebarrell
Champ in-the-making
Champ in-the-making
Thank you for that!

mwahnschaffe
Champ in-the-making
Champ in-the-making
This is an important feauture for me, too..

trademak
Star Contributor
Star Contributor
Okay, we'll be looking at this for the next release.
We have to create an extra validation step to make sure an Id is unique within the diagram.

Best regards,

ronald_van_kuij
Champ on-the-rise
Champ on-the-rise
Afaik, xsd validation does this since the id's are defined as id's (must be unique) so it might be that you do not need to do much at all.

tiesebarrell
Champ in-the-making
Champ in-the-making
Yep,

but we need to validate the diagram (.activiti), not the resulting output (.bpmn20.xml) and there's no XS validation on the diagram AFAIK. We also don't perform XS validation on the BPMN atm I think, because most validations are in a separate module.