Update Widget¶
As the Widget is by default hosted by Isogeo in SaaS mode, code updates are carried out by the Isogeo team. As soon as the Widget is put into production, a new URL containing the new version is generated.
However, since the Esri portal caches the Widget code, in order for the new Widget to be loaded, you must either :
- recreate the extension item in the Portal with the new URL and replace the old Widget with the new one in each application.
- or modify the url entered in the existing extension(s) with ArcGIS Assistant.
This URL change is mandatory to force the portal to reload the new Widget code into its cache.
Note
If you're hosting the Widget locally, you'll first need to create a new folder on the server to store the new version, then follow the same steps with ArcGIS Assistant to specify the new URL.
With ArcGIS Assistant¶
If you haven't already done so, set up ArcGIS Assistant for your Portal, or go directly to step 10.
- Create a
Web Mapping
application and specify the urlhttps://assistant.esri-ps.com/
- Name it
ArcGIS Assistant
and fill in the tags and summary - In the application settings, click on
Save
- Choose application type
Browser
- Enter the redirection url
https://assistant.esri-ps.com/
and click onAdd
, thenSave
- Recover
application ID
- Open
https://assistant.esri-ps.com/
and choose to connect with ArcGIS Enterprise - Enter your portal URL and application ID
- Log in with your administrator credentials
- In contents, click on the Widget extension item, then on
View Item JSON
- Click on
Edit JSON
and enter the new URL supplied by Isogeo in theurl
field - In the
Data
tab, modify theversion
field to indicate the new version supplied by Isogeo - The Experience Builder applications in which the Widget is integrated retrieve the Widget item via its
id
, and thus the new code url in the process. So there's no need to reload the Widget in each application using this method.