Add element Id refresh/rebuild button

Based on conversation from #380

The element ID is set on the initial creation of the element on the canvas.

When a user adds a Task element, the ID is set to something like: Task_1u62ryy Currently, when a user changes the task to a User Task, the ID remains the same.

Proposal:

Allow the user to manually refresh/rebuild the element ID based on automated naming convention such as Task_1u62ryy becomes UserTask_CallCustomer_1i87o9i.

Current proposal for for naming convention: [element type]_[element name]_[generated short UUID] The short UUID ensures that if there are two elements with the same element type and name, the UUID will still be unique.

If we wanted to get really fancy 😸, this could be a configurable property of the modeler allowing someone to create a “pattern” to follow based on Tokens/Slugs. But I think that is just “flashy” rather than having a strong use case for a v1.

The user will have to manually refresh the IDs and will not be automatic when the element type is changed.

Could see use cases for an ID refresh on an individual element and in Bulk. Bulk Scenario: user creates the BPMN and after the overall “design” is established, the user “refreshes” all ID values so they correspond with the proper naming convention.

Example scenario where being able to easily refresh the ID is helpful:

Where the End event was changed to a Intermediate event, but the ID is still indicates it is a End Event.

Or:

Where the Task was changed to a User Task, but the ID still indicates it is a generic task.

[StephenOTT]

@nikku here is another scenario where this would be helpful.

You convert a Task into a Sub-Process. The ID remains with the original Task name.

[berndruecker]

Hey Ingo.

Please not that it should be assertThat(processInstance).isWaitingAt(“receiveTaskReceivePayment”).hasPassed(“sendTaskSendInvoice”).

According to our best practices: https://camunda.com/best-practices/naming-technically-relevant-ids/

Cheers Bernd