Latest Contributions by BrianWilson3

‎09-14-2020

In large organizations some surveys are often downloaded by default as almost all users use them. In my organization we have around 10 standard surveys that every user downloads. When the Survey123 app updates or is reinstalled, the downloaded surveys are cleared and the users must remember which ones to re-download. I would like to see the ability for an administrator to set a survey as auto or manual install, manual by default. When a user enters the Portal URL and signs in, the app automatically sees these surveys as needing to be downloaded and does it. This would eliminate time for the end user having to figure out which ones he/she needs and unnecessary calls to admins.

‎07-09-2020

Using the new build of Collector got us around that issue. Collector Aurora. As far as Explorer, I believe this issue has been resolved. The current build out for Android is 20.2.1. I am able to open maps without getting the untrusted host error.

‎02-28-2020

Chris, This is currently in beta. Thanks, Brian Sent from my Verizon, Samsung Galaxy smartphone

‎12-20-2019

It is very frustrating. It is unfortunate that we've had to work around this issue in this way. Sent from my Verizon, Samsung Galaxy smartphone

‎12-19-2019

I would also like to know when 10.8.1 will be available.

‎12-19-2019

Sure Tom. I must warn you though, i'm sure ESRI frowns upon editing the base code of their widgets. I always create a backup copy of the file prior to editing anything in the Portal file system. On your Portal server, navigate to Program Files\ArcGIS\Portal\apps\opsdashboard this folder. Make a backup copy of the index.html file. edit the original index.html file in the head section, add this meta refresh tag, i grouped it in with the rest of the metas. <meta http-equiv="refresh" content="1200"> Save the file, clear your browser cache and give it a try. 1200 second refresh equals 20 minutes. Even though the app crashes at 30 minutes, i was still seeing some issues with the refresh at 25 minutes. This tag will just refresh the entire page and grab a fresh token every 20 minutes. As our dashboards are crucial to operations here and are displayed on our video wall, having to F5 the dashboard every 30 minutes wasn't an option. Hope this helps.

‎12-18-2019

Excellent, thank you john. I look forward to 10.8.1 Sent from my Verizon, Samsung Galaxy smartphone

‎12-18-2019

John, Looking at the bug you referenced I dont see the same behavior I am experiencing noted. Ours will log in just fine initially, after 30 minutes it prompts for auth when it shouldn't being iwa and sso. Can you confirm you have seen this behavior and it's fixed in the 10.8.1? I want to make sure its documented and fixed so it is resolved in 10.8.1. Thanks, Brian Sent from my Verizon, Samsung Galaxy smartphone

‎12-18-2019

Excellent, thank you John. I will give my current case worker the bug you've provided. Sent from my Verizon, Samsung Galaxy smartphone

‎12-16-2019

As it looks like ESRI is getting the WAB token timeouts and the OpsDashboard token timeout mixed up, i have reopened my closed case with #BUG-000127276 on it. I will let you know what bug number i end up getting out of this. If one ESRI person would have reached out to either of us and asked if the issue was resolved prior to closing the bug/case this could have been fixed much sooner. I have started a new thread under the Ops Dashboard group and referenced this thread in it. Hopefully we'll get some more visibility starting fresh.https://community.esri.com/message/897671-ops-dashboard-token-expiration

‎12-16-2019

Has anyone had any luck getting ESRI to fix the token timeout issue with OpsDashboard and IWA/Portal? I opened a ticket back in August and have yet to get a resolution. Environemnt: Portal 10.7.1, IWA auth, Operations Dashboard web client. Behavior: Initially SSO works and the dashboard comes up, after exactly 30 minutes the token expires and the app prompts for auth. If i signin, it prompts multiple times for sign in and eventually lets you through. I have been able to temporarily "fix" the issue by added a meta refresh tag at 25 minutes into the Ops Dashboard HTML. My original Bug number was #BUG-000124152 which was marked as "Not in Current Product Plan" in early December. In the case it mentioned that i was actually experiencing #BUG-000127276, which BTW was resolved in 10.7? I am still experiencing the issue but have reopened the case. This seems very similar to the token timeout that WAB was seeing in 10.6/10.6.1 which was resolved in 10.7. It would be great if someone from ESRI would reach out to atleast a few people affected by these bugs and ask if it was resolved. The original thread where this was first mentioned was here https://community.esri.com/message/897492-re-wab-token-expiration .

‎12-13-2019

I am seeing the exact same behavior. Did not see it in 10.6.1, saw it starting in 10.7.1. Ended up adding a meta refresh tag into the html at 25 minutes to get around it. Same case for us where the bug was marked as closed and not in product plan. We were assigned a different bug which I had to get added to our account. Seems easy to test and reproduce, why cant this be fixed in a patch? Sent from my Verizon, Samsung Galaxy smartphone

‎08-22-2019

I see this is in the "Product Plan". After testing this morning i agree being able to work in an offline state would greatly benefit our company. What needs to also be address is the instant sign in when first opening the app. If i have the app open i can see assignments and just not work them. If i then put the app in airplane mode it shows offline but still allows me to see the assignments. If for whatever reason i close out of the app and reopen it fails to open the app as it cannot sign in to our Portal. For our current project being able to see the assignments and their details would be enough but if somebody accidentally closes the app and cannot see anything then we're dead in the water.

‎08-02-2019

Just a heads up for everyone experiencing this issue that it does appear to be at least partially fixed. After complaining to support that it was not fixed in 10.7 or 10.7.1 and doing some troubling shooting we found what appears to be a promising result. If you upgraded from 10.5,10.6,10.6.1 to 10.7,10.7.1 the 30 timeout is still hidden in the background somewhere. To fix this i simply had to open up the token settings in AGS and update, save to reapply them. After than i'm seeing tokens last longer than 30 minutes. Issue 2 i'm dealing with an have a bug logged for is the OpsDashboard timing out after 30 minutes. It appears the tokens for that are still expiring at the 30 minute mark causing the OpsDashboard to prompt for sign ins for each data source even though IWA and SSO are enabled.

‎08-02-2019

Just a heads up this appears to be fixed in 10.7.1. What they don't tell you is that you have to go into the token settings for AGS and reapply them in order to make them stick this time. I'm currently testing and am seeing tokens successfully last past 30 minutes.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by BrianWilson3

Survey123 Default Organization Surveys

Re: Explorer app (Android) - untrusted host

Re: Allow working offline in Workforce app

Re: Ops Dashboard Token Expiration

Re: Ops Dashboard Token Expiration

Re: Ops Dashboard Token Expiration

Re: Ops Dashboard Token Expiration

Re: Ops Dashboard Token Expiration

Re: Ops Dashboard Token Expiration

Re: WAB Token Expiration

Ops Dashboard Token Expiration

Re: WAB Token Expiration

Re: Allow working offline in Workforce app

Re: WAB Token Expiration

Re: token expiry

Re: Repeated Login Prompts When Already Signed In

Re: Indicator Widget Not Returning Correct Value

Re: Cache issue with Chrome - widgets not updating

Re: Cache issue with Chrome - widgets not updating

More Advanced Measurement Tool