GP tools experience builder

2319
4
06-08-2023 06:53 AM
LiveHus
Emerging Contributor

Hello 😎

I am currently planning an upgrade from AGE 10.8.1 to 11.1 and I am responsible for outlining the migration from Web App Builder to Experience Builder. The existing WAB consists of several geoprocessing tools and analysis that needs to be customized to Experience Builder - some examples are: service areas, route directions, buffer tools and different search and filter functions.

However, I am somewhat confused regarding the implementation of GP tools in custom widgets. Does anyone have experience with this? Is this possible?

Any tips would be very helpful.

Thank you!

4 Replies
Johannes_NL
Emerging Contributor

I have the same question.

0 Kudos
JanSarata
Esri Contributor

Hello @LiveHus,

regarding the widgets which are present in WAB and not yet present in EXB, you can check out this link: https://community.esri.com/t5/arcgis-experience-builder-documents/functionality-matrix-for-web-appbu...

Regarding the widget to use GP Service, it is not currently present in EXB, but it should be in the end of this year.

AnnieD_WLP
Occasional Contributor

Any update on this? It's already end of 2024. Thanks!

AValenski
Occasional Contributor

@LiveHus & @Johannes_NL : Please note that there are significant, prohibitive gaps in functionality in ExB and I am no longer recommending clients migrate, but instead invest in self-hosting their existing WAB apps (and the underlying JS SDK) to ensure your apps continue to function. Perhaps one day ExB will approach parity to WAB, but that seems to be years away still. 

The current release of the 'Analysis Widget' is woefully underdeveloped. If your existing GP Widgets use Map Services as inputs, require user input geometries (i.e. users draw/sketch on the mapView as an input), or if GP tools generate client-side graphics/layers/results, then the current 'Analysis' widget will not meet your needs, even with custom GP Services.

Unfortunately, this pattern isn't restricted to the Analysis widget, but most "implemented" widgets.