Why does Dataiku allow two web-apps with the same name?

I was surprised to find Dataiku allows two web-apps with the same name to exist. Why? The expected behavior would be to ask the user if they want to overwrite a published web-app when name collision occurs. thx
Operating system used: WIndows 10
Answers
-
Turribeach Dataiku DSS Core Designer, Neuron, Dataiku DSS Adv Designer, Registered, Neuron 2023 Posts: 2,236 Neuron
Because internally Dataiku uses the WebApp ID which is appended to the name to form the WebApp URL.
-
@Turribeach But does this behavior make sense from an end user perspective? This type of behavior is commonly frowned upon as there is no way to know from the URL which is the most recent version. What advantage is there in allowing this?
-
Turribeach Dataiku DSS Core Designer, Neuron, Dataiku DSS Adv Designer, Registered, Neuron 2023 Posts: 2,236 Neuron
No, it doesn't but you shouldn't be using the WebApp ID in the URLs that end users use. Those are for you to develop and test Webapps. What you should do is to setup a vanity URL. This is done in Settings ⇒ Security & Audit ⇒ Other security Settings ⇒ Authenticated webapps ⇒ Vanity URLs:
Once you do this you will be able to hit your webapp at /webapps/mywebapp/ whereas you will continue to use the /webapps/WebAppID_WebAppName/view URL for development and testing. The vanity URL not only allows for a much user friendly and simpler URL but also removes the Dataiku framing giving you full power to develop a nice looking webapp. In addition to this you can also easily switch with two different versions of your webapp (ie during major releases/changes) by simpling changing the vanity URL mapping between two different WebApp IDs. This is turn allows for easy roll back and parallel development of the same webapp in multiple code bases.