Workflow can be renamed even if it's in an ancestor package and it leads to model inconsistencies

bugs
1

I was trying to rename an ancestor workflow. The worflow is extended in a current package (two wf steps). Ona wf step was opened (in the document window). The rename was actually conducted (I changed the name of the workflow and pressed ctrl+S). Then I edited something in one opened step and then I saved the edit.

I was expecting the worflow to be renamed OK.

Instead I’ve got model inconsistencies. The steps in the extension packages were divided into two. One was renamed, the second one was not renamed (probably the opened one).

I think the problem is that Architect allows to rename a workflow in an ancestor package and can easily lead to confusion.

Any element must be strictly prohibited from editing when in ancestor package.

2

Unfortunately, I can’t replicate the problem. It seems it’s not possible to edit name of the worflow, if it’s defined in the ancestor package. Nevertheless, I experienced it as described or slightly different.