Why Appian allows name duplicacy in Process Model

I am working on Appian 17.3 and I am aware that Appian does not allow users to create duplicate name Expression rules, interfaces , constants etc.

But why Appian allows  same name (Name duplicacy) for more than 1 Process Models.

  • If we have more than 1 Process models having same name, it will cause inconsistency and complexity for developers while adding Existing Process Models in Applications.

I have created 2 Process Models having same name and Appian is allowing me to do it.

Any Suggestions Appreciated

Parents
  • I have been in a situation where it was necessary to have process models with the same name because related actions can only have the direct text from the process model name. One way we found that made it possible to tell a difference was by adding a "." to the end of one of the names and ensuring the team knew what the difference was between the two models.

    The UUIDs are different but that doesn't help when making a change from /design to one or both of the models.
Reply
  • I have been in a situation where it was necessary to have process models with the same name because related actions can only have the direct text from the process model name. One way we found that made it possible to tell a difference was by adding a "." to the end of one of the names and ensuring the team knew what the difference was between the two models.

    The UUIDs are different but that doesn't help when making a change from /design to one or both of the models.
Children
No Data

 Discussion posts and replies are publicly visible