Select to view content in your preferred language

Linking to a page in app by URL (rather than by page) results in splash screen always being shown

166
0
4 weeks ago
Labels (1)
NicoleJohnson
Frequent Contributor

I'm seeking ideas or explanations for this.

Basically, I'm using a table to hold links to the pages in my experience, and to describe those pages dynamically in a list widget.

First, the user searches something in a search widget (e.g., "disease"), and if there are any results, a "search results" window opens with the aforementioned (now filtered) list widget. I've configured the list widget and a button widget within the list widget to link to the URL in the table, and I've chosen to open the link in the app window.

NicoleJohnson_1-1747833758153.png

While the link DOES open in the app window, the splash screen also re-appears.

The splash screen is non-negotiable. I can't do any tricks like undoing the splash screen status and just having that window open with the home page, because people can send links to each other from one of the other pages and miss the faux splash screen entirely. Same goes for URL parameters--people can just alter those.

I'm not even sure I can get away with allowing the "don't show this again" option for the splash screen, which wouldn't solve this problem but would make it slightly less annoying for users. It would be annoying to have to check that box in the first place, though.

I've tried all of these options without success:

NicoleJohnson_0-1747833302328.png

I've also tried just creating a button outside of the list widget entirely, linked to a page in my experience (not by choosing "page" in the "link to" options, but choosing URL. It seems that by choosing URL, the page expects that I'm going somewhere else when I click that, and "forgets" that I was there?

 

Edit: I should mention, I could just use the menu widget or create something similar, but I'm essentially recreating an existing application (not built in anything Esri). This existing application offers the navigation functionality I'm after, and it's something the stakeholders have said multiple times is something they really like. A menu etc. isn't going to tell them what a page is about or be findable based on keywords in the way that they want/are used to seeing.

0 Kudos
0 Replies