Webappbuilder Widget Tutorial 1 Quick Start

by Li Yuanxiang

Webappbuilder is a powerful tool for configuring applications on ArcGIS Portal and arcgis.com. Reasonable use of Webappbuilder's micro-components, can realize the application of 0 code customization, and can effectively solve the relevant practical application problems.

1. Start Webappbuilder. Webappbuilder needs to be supported by ArcGIS Portal or arcgis.com and cannot be directly connected to ArcGIS server, so you cannot configure your application as a simple ArcGIS server. This is not the same as the previous flexviewer. The Webappbuilder is divided into built-in and developed versions, and the built-in version is embedded directly in ArcGIS Portal or arcgis.com, and must be logged in to the above two platforms before it can be used. The development version can be downloaded from the ArcGIS developer site and run locally, but must be connected through the application ID when used. The following interface runs Webappbuilder directly under ArcGIS Portal or arcgis.com, as

After entering the necessary headings, tags, and summaries, run the following interface, you can choose the theme of the application (layout and style of the interface, etc.), the map (which webmap to load), widgets (functional components), attributes (some additional notes of the application)

2. Classification of widgets. Since the main introduction is the use of widgets, here are some basic operations for other topics and maps are ignored. After selecting the theme and map, go to the widget selection screen, such as

Widgets are generally subject to subject matter, typically divided into two widgets in the configured application, one floating widget and one panel widget. Floating widgets are floating directly on a map control, and generally behave like zoom controls, positioning buttons, and retrieval controls, without having to bring up specific panels to perform operations. The panel widget, as the name implies, is a widget that can bring up a panel interface, which is displayed as a specific button, and the interface that pops up and results when clicked, generally behaves as a button on a map control and a button on a toolbar.

3. Features of the widget. Custom applications are basically understood to use widgets, because the interface layout of the application is a fixed set of templates, of course, if it is an advanced developer, but also according to Webappbuilder specifications to customize these templates, not detailed here. As a result, the use of widgets is the key to application configuration. We can open the widget controller to see the inside of the micro-category, roughly the following, according to the ArcGIS Portal or arcgis.com version, there will be different widgets, in general, the higher the version of the widget will be more, is the ArcGIS Portal 10.4 widget.

4. Use Widgets. Can be used in three aspects of the widget, the bottom of the button with a digital label, which corresponds to the map control floating button, the click Will jump to the widget selection interface, after the selection of the widget, there will be a button icon with the control; the middle part is the so-called Floating widget section, corresponding to some non-pop page control, such as scale bar style, zoom slider, full-scale operation, etc., the top is the header controller, popular point is the navigation bar button, the configuration of the widget in the navigation menu generated by the corresponding button icon, click to eject the function of the widget. The corresponding locations of the various widgets are shown below.

Each widget has its own unique role, so the configuration is not the same, we first look at some features of the floating widget. For example, the scale widget, click on its edit button (mouse slide to the widget icon, will display a small pen small icon, click on the small icon to enter its configuration interface) will pop up some of the scale bar settings, such as the scale of units and styles. Since the scale does not need to be clicked, it is associated with the scale of the map, so the icon for that widget cannot be changed.

The same is the floating widget, look at the search widget, click to see its default configuration is to use ESRI's GeoCode service to perform the search, as shown in

If we have other geocode services or have our own need to retrieve service layers, such as Mapservice, Featureservice, can be configured here, to implement the search function. The following action adds a layer of one feature service to the search widget for global retrieval. Click Add Search source to add a feature layer

The added feature service can be selected from the loaded WebMap already configured, either directly from the portal hosted service or directly into the address of a feature service, such as the portal hosted feature service, which can be retrieved directly from all services under the portal account.

After clicking Next, the widget retrieves all the layers under the feature service, such as a layer with only one Zhandian under the feature service, selects it, and performs the next configuration.

After selecting the data source, you can set the specific parameters of the widget, such as the contents of the Search (field), the alias of the title, maximum number of results, exact match or fuzzy search, etc.

After saving, you can use the "Start" button to view specific configuration conditions, such as

If you want your application to be able to access your Web pages directly, you can use the preview method to view its specific content and set the resolution of the supported mobile devices, such as

In this way, a simple function can be completed. You can configure more widgets for your application to accommodate different usage scenarios.

Webappbuilder Widget Tutorial 1 Quick Start