Select to view content in your preferred language

Allow Pointing and Repointing of URL to ItemID in Enterprise

65
1
14 hours ago
Status: Open
DarrylHilton
Regular Contributor

When new itterations of Experience Builder Applications, Dashboards etc are created a new Item is created and therefore a new URL. This then means resending the new URL to all known users of an application, changing links on web pages and so forth. Usersw often retain old links which will then lead to a non existent URL or and old application.

It would be useful for there to be a kind of Url Landing Page directory with a static URL which autoforwards or refers to an application or other item. This static URL should then have the ability to change the item it is directing towards, therefore keeping the URL users use the same but using the new application. Currently this can be done in IIS on a web server if users have access to one, but adds another vulnerability point, access requirement etc

For example users always access http://mysite.domain.com/portal/nicemap.html but the item this refers them to is changable.

This would also more closesly follow a dev/test/prod upgrade release cycle

1 Comment
berniejconnors

@DarrylHilton,

        We solve this problem by building a very thin web page and then use an iframe to embed the ExB URL into the web page.  This way we can control and maintain a URL that never changes on our own webserver.  Here is an example we have been using since 2009.  Feel free to look at the page source (<Ctrl-U>) to see what I mean - https://geonb.snb.ca/geonb/index.html.  Over the years this URL has pointed to a FlexViewer, Web App Builder, and an Experience Builder app.  The key is to never share the ExB URLs with your users because you know some future change will inevitably create a new item ID. 

        We use our own Linux web server for this but you could do something similar with ArcGIS Enterprise Sites or ArcGIS Hub.

Bernie.