Currently (at least for v6.9) a BP environment is basically identified by the connection name. The connection name is a free text that can be changed anytime.
When working with multiple teams in multiple environments it is important to exactly know what environment we are working in and talking about.
Avoiding ambiguous names like 'My BP 123', 'old/new BP', ... might be avoided to some degree with naming conventions and using scripts instead of manual configuration.
But still, changing the name of the connection or keeping the name but changing port, can lead to confusion.
It would be nice to have the possibility to specify a name to identify a BP instance / environment and that is stored in the DB. This can the be displayed in the client. This name could also be added during archiving and reduces the risk of corrupting the target archiving structure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.