topic Re: AGO Experience Builder Analysis Widget in ArcGIS Experience Builder Questions

AGO Experience Builder Analysis Widget

BrettMartin1 — Fri, 01 Mar 2024 16:50:51 GMT

We have a public geoprocessing service in this AGO application in WAB. I have been testing the most recent updates to the Analysis Widget in Experience Builder. The ability to draw the input parameter on the map is a great improvement. However, the widget is still missing functionality that is available in the WAB Geoprocessing Widget. The input configuration is missing “use current map extent” for the extent parameter. There are not options for configuration of output popup or symbology.

The major issue we have found is there is no way to configure the widget to not create a feature service. In WAB if I uncheck “Visible”, the results are added to the map and not too AGO My Content.

In Experience Builder, there is no option in the builder. The hint in the app GUI states if left blank a feature service will not be created.

However, if left blank the tool fails.

Re: AGO Experience Builder Analysis Widget

SteveCole — Fri, 01 Mar 2024 16:45:18 GMT

ESRI has claimed that AGO EB will achieve WAB parity by the ESRI UC this year so it remains to be seen how this will all shake out. The Dev team is maintaining this post which lists the WAB/EB widget list overview. As with all things ESRI, I'm pessimistic that they'll reach parity without removing *some* functionality under the pretense of progess.

Oh, and add 6 months to the specified timeline if you're using Portal EB as it is the last product the chain to receive updates.

Re: AGO Experience Builder Analysis Widget

AValenski — Tue, 26 Mar 2024 09:25:20 GMT

ExB is an exercise in moving goalposts. That post is laughably inaccurate. Just looking at the first column, you can tell several of the "completed" apps do not have parity and seemingly will not. The first four (4) items marked as "Migrated/Complete" all have no parity, in addition to the catalog of bugs identified:

1. About Widget - Removed completely, but similar functionality can be achieved via configuring Card Widgets, Modals, or other. Additional HTML limitations. Calling this "done" is ... suspect.

2. Add Data - Arbitrary and inflexible limitations imposed (shapefiles limited to 4,000 records/2 MB; csv limited to 1,000 records/10 MB and must have [detectable] spatial fields; geojson limited to 4,000 records/1 MB); popups will not read attributes from files that are added; layer-order chaos when adding layers; no symbological customization; cannot use added data in other widgets. Adding KMLs had/has a bug where it appends an additional (/), causing it to fail.

3. Analysis - Not a complete product. Released before it was done. Still no parity.

4. Attribute Table - functions completely differently; requires individual layer configuration rather than global enablement; missing map action (view in attribute table); disconnection between map source and attribute table; differing filtering/querying/map-extent functionalities; no support for Web Map Arcade fields.

Re: AGO Experience Builder Analysis Widget

SteveCole — Tue, 26 Mar 2024 15:02:49 GMT

No argument for me here as I agree 100 percent. This winter I was faced with either migrating to EB or extending code base in a 3.x app I have to support and I eventually chose the later. I didn't want to but EB is so laughably lacking in functionality there really was no choice. I will likely switch to EB at the end of this year since I don't want to migrate my JS app to 4.x but I am fully expecting the EB to be lacking features even a WAB app would possess. When a company doesn't have a viable competitor, this is the end result- you get what you get.

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Fri, 29 Mar 2024 04:06:02 GMT

Hi @BrettMartin1 ,

Thanks a lot for your feedback!
We are catching up the functionalities of Geoprocessing widget in WAB gradually. So we will support “use current map extent” in future release.

For the failure you saw in ExB when leaving feature service name blank. Do you mean this tool can succeed if you provide a feature service name? Could you share your service by any chance to us for a further look?

Re: AGO Experience Builder Analysis Widget

BrettMartin1 — Fri, 29 Mar 2024 10:00:19 GMT

Hi @Wei_Ying

Thanks for you getting back to me. I am receiving the error below signed into AGO when I do give an output name.

Here is the GP Service: https://www.fairfaxcounty.gov/gisgeoproc/rest/services/LDSA/Drainage_Area_Delineation_Tool/GPServer/Drainage Area Delineation Tool Ref

Flow Accumulation Service (reference layer): https://www.fairfaxcounty.gov/gisimagery/rest/services/WatershedDelineation/FlowAccumAcres2018rev2022/ImageServer

Here is the WAB app: https://fairfaxcountygis.maps.arcgis.com/apps/webappviewer/index.html?id=cadf1f2929d34220b32d23d968541d27&mobileBreakPoint=300

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Fri, 12 Apr 2024 00:59:11 GMT

@BrettMartin1 Thanks a lot for providing the data. We will take a further look.
What error did you see when you do not give a output service name?

For the error when you providing the name, it is because the server hosting this GP service does not allow you to write data to it so you cannot creating the output feature service you named. You have to check the portal permission. Please check https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/share-analysis/use-web-tools-with-output-feature-class.htm

The portal user must have privileges to create an output feature service. The only roles with this privilege are Publisher and Administrator. For portal users with a custom role, that role must have Members/View, Content/Publish hosted feature layers, and Content and Analysis/Standard Feature Analysis privileges.

Re: AGO Experience Builder Analysis Widget

BrettMartin1 — Mon, 15 Apr 2024 11:02:25 GMT

This is a public service published to Standalone ArcGIS Server. The app has public users that do not have AGO accounts. We do not want users to create an output service. We need the same functionality that is in the current WAB geoprocessing widget.

Below is the error message when we do not give an output service name. When you make this not visible in WAB there are no issues. See the app I sent above.

Re: AGO Experience Builder Analysis Widget

MarcusRademaker — Wed, 15 May 2024 15:16:01 GMT

Hi @BrettMartin1,

How did you manage to get the error messages? My script for a GP tool uses arcpy.AddMessage and I changed the parameter settings (properties - message level) of the GP tool to Info. In WAB it works just fine, but in the Analysis widget for ExB developer edition it only generates the start/end/elapse time.

Hope you can help me!

Regards,

Marcus

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Mon, 03 Jun 2024 23:12:21 GMT

Hi @BrettMartin1 ,

I have logged an enhancement request for controlling parameter visibility of custom tools.

Thanks,
Wei

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Mon, 03 Jun 2024 23:13:43 GMT

@MarcusRademaker would you be able to share the go tool to me so we can take a further look.
If the message display on WAB but not ExB it should be a bug.

Re: AGO Experience Builder Analysis Widget

MarcusRademaker — Mon, 10 Jun 2024 13:29:28 GMT

@Wei_Ying Here is the URL: https://portmapsacc.ad.portofrotterdam.com/porags6/rest/services/UpdateFeatures2/GPServer

However, maybe you cannot enter it due to our firewall. In that case, what's your email address?

Re: AGO Experience Builder Analysis Widget

BrettMartin1 — Tue, 23 Jul 2024 17:29:12 GMT

Hello @Wei_Ying

The tool is now working! However, after testing several other tools I have several new requests. We had the ability to configure the output pop up in WAB.

Also, I love having the ability to have multiple GP services in one widget. However, can we get an option to edit the names of the tools? Seems to be pulling straight from service name.

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Fri, 02 Aug 2024 02:06:38 GMT

Hi @BrettMartin1 Thanks for the feedback. For your request.

We had the ability to configure the output pop up in WAB.

So far we don't have that plan. But in future we may enhance to support.

Also, I love having the ability to have multiple GP services in one widget. However, can we get an option to edit the names of the tools? Seems to be pulling straight from service name.

We are working on enhance to rename the tool label.

Thanks,
Wei

Re: AGO Experience Builder Analysis Widget

PaulDziemiela21 — Wed, 27 Nov 2024 15:51:08 GMT

Hi folks,

I got caught up in the topic without realizing that the Summer 2024 update has apparently reverted the EB Analysis widget back to how the old WAB GP widget works. At least it seems so. Brett and Wei, is that correct?

Is it a fair statement to say the EB documentation is lagging in explaining this? I still see statements about the Analysis widget needing an AGO account to use.

Also it now seems like the option to directly load GP services results into a hosted feature layer is just kaput. I suppose I was hoping for both options where if one is logged into AGO then the latter option is made available. Is that in the future widget roadmap?

Paul

Re: AGO Experience Builder Analysis Widget

BrettMartin1 — Mon, 02 Dec 2024 20:58:44 GMT

There have been no changes to the tool even with the most recent November update. We are planning to move this GP service to a VertiGIS workflow once WAB is no longer supported. We have already done so for internal application. Not sure why esri cannot at least provide the functionality that exist in the WAB geoprocessing widget. Folks have business processes built around these tools.

Re: AGO Experience Builder Analysis Widget

BrettMartin1 — Mon, 02 Dec 2024 21:11:29 GMT

I see we can change the name of the tools now, thank you.

We need the ability to configure the pop up of the output.

More importantly we need to same options from WAB for the extent parameter. Currently users will have to draw a polygon for the extent of processing since "current map extent" is not an option like WAB.

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Fri, 06 Dec 2024 02:26:30 GMT

Thanks for you feedback. We will try to support these features in future releases.

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Fri, 06 Dec 2024 02:34:09 GMT

Hi @PaulDziemiela21 Thanks for your feedback.
>> "Summer 2024 update has apparently reverted the EB Analysis widget back to how the old WAB GP widget works. "

What does this mean? Analysis widget in ExB actually combines Analysis and Geoprocessing widgets you see in WAB. So it can run both Esri provided standard tools and custom gp tools.

>> "Analysis widget needing an AGO account to use. "

Not really. If you are running the custom web tool (gp service) only, it does not require any account if the gp service is public accessible. But it you are running the esri provided standard analysis tools you need to login your AGOL or Enterprise account.

>> "Also it now seems like the option to directly load GP services results into a hosted feature layer is just kaput. "

The result is not always write into a hosted feature layer. You have option to output feature service, otherwise the result layer is just temporary unless you export it as an item or other format.

Re: AGO Experience Builder Analysis Widget

Wei_Ying — Fri, 06 Dec 2024 02:35:10 GMT

@BrettMartin1 we have implemented most of the functionalities from WAB. What exact functionality are you looking for?