Latest Contributions by Jianxia

A preview of the new features in Experience Builder for the June release of ArcGIS Online, which is scheduled to be available in late June 2025. We'd like to highlight support for authoring Arcade expressions. In addition, the Emergency Response Guide web tool is now available, which substitutes the Emergency Response Guide widget from Web AppBuilder.       ... View more

A sneak peek into new features in Experience Builder in ArcGIS Enterprise 11.5 planned to be available in May 2025.  ArcGIS Enterprise 11.5 picks up new features from ArcGIS Experience Builder in ArcGIS Online November 2024 and February 2025 releases. We'd like to highlight Express Mode, a simplified app building like WAB. Please check the following blogs for the upcoming new widgets and capabilities in 11.5. What's New in ArcGIS Experience Builder (November 2024) What's New in ArcGIS Experience Builder (February 2025) Cheers, ... View more

Version 1.17 of ArcGIS Experience Builder developer edition is now available for download. In addition to picking up new widgets – Oriented Imagery Viewer, Processing Templates, and Flow Row–and other highly anticipated enhancements from the February 2025 release of ArGIS Experience Builder in ArcGIS Online, Version 1.17 allows you to add help documentation for your custom widgets and facilitates the easy deployment of your apps using the same client ID that you used when installing the developer edition. Let’s explore them. Add help document to your widget When developing a custom widget, you might want to include a help document that explains how to configure and use the widget, like the built-in widgets. You can accomplish this by creating a folder called "doc" within your custom widget directory, and then adding a file named "index.html" in that folder containing the help content, as illustrated below. When you add a widget and click the question mark on the widget setting panel, the help link should open as demonstrated below. For additional details, refer to  Add help to your widget. App deployment using Client ID registration for Developer Edition Before this update, if the application included private data from a portal, it was necessary to input the client ID in the app's config.json to activate OAuth authentication prior to deployment. With the latest release, when the data originates from the same portal as the developer edition, you now have the option to streamline the process by choosing "Apply builder client ID" during the app download. Consequently, the client ID associated with the builder will automatically be integrated into the config.json file of your downloaded application. Code samples The Share Code Entry Dynamic sample dynamically load the share code as demonstrated below: import { moduleLoader } from 'jimu-core' moduleLoader.loadModule('widgets/shared-code/entry', props.context.folderUrl) The Web Worker sample demonstrates how to use Web worker in your widget. It uses ${props.context.folderUrl}dist/runtime/assets/worker.js to load the web worker script and then use postMessage() to communicate between the widget and the worker. Breaking changes There are breaking changes in Jimu libraries that may affect your apps. For example, all data source related interfaces are moved to jimu-core and more lint rules are added. Make sure to check these changes out before upgrading your apps. For more information about the 1.17 release, see What’s new. You can reach us with any questions at experiencebuilder@esri.com. Thank you, The ArcGIS Experience Builder Team Subscribe to our newsletter to receive the latest ArcGIS Experience Builder updates, news, and content. ... View more