What's new 1.1
We are introducing a new component inside Experience Builder called Storybook. This powerful capability provides you with a view into the UI components for the jimu-ui library and the theme system. It also provides the API docs to help you build the UI for your experience.
Several new samples are added, some of these include: how to utilize 3rd party libraries in your widget, editing features in a map, and how to use redux to share state between widgets. Here are the newest samples:
We have added support for unit testing using Enzyme/@testing-library/react and Jest as part of our release package. The @testing-library/react is recommended.
We have added support to install Experience Builder without an internet connection. See the install guide for more information.
We have also made the documentation available for offline use.
ArcGIS Experience Builder includes three new widgets, support for more data types, new animation styles, configurable windows, and more themes, templates, and quick styles. Some of the highlights are listed below.
- Animation—Set eye-catching animation styles on pages, windows, and widgets using effects such as fly-in, spin in, and fade in. You can also set transition modes for moving between section views.
- Data types—You can now connect to more data types, including feature service, map service, group layer, and feature table.
- Data views—Create data views of feature layers by adding filter and sort criteria to control what appears in connected widgets.
- Data refresh interval settings—Keep the data in your app updated automatically.
- Templates and themes—Start with one of many new default templates, including two multipage templates. Two more themes have also been added.
- Windows—Configure windows that appear when the app or a page loads, or when activated by another widget. Include custom splash screens, confirmation messages, and alerts in your web experiences.
- Guided tour—For a quick start, follow guided instructions that step you through configuring an experience or a List widget.
Several widgets have more settings and styles, including Views Navigation, Text, Menu, Feature Info, List, and Fly Controller. You can pin a widget to keep it visible on scrolling pages and rotate widget's for more flexibility. Use the new widget operations to duplicate widgets and copy and paste them across pages for streamlined page design. Other improvements include the following new and updated widgets:
- Bookmark widget (new)—Provide a collection of 2D and 3D spatial bookmarks for a selected map. Use the provided templates to add rich detail for a place, such as images, descriptions, links, and embedded apps. The traditional templates allow end users to create bookmarks at runtime.
- Card widget (new)—Display related bits of content in a flexible and extensible container that supports hover effects. Use one of many classic or advanced templates or design your own.
- Divider widget (new)—Separate widgets with a visual line to improve page structure.
- Filter widget—Choose from several new arrangement and activation styles. There are also more input styles for ask-for-value clauses, more supported operators, and duplicate clause and clause set have been enabled.
- Image widget—Populate image widgets from feature layer attachments and web map feature symbols.
- Map widget—You can now add the Select tool to your maps or scenes.
- Removed theme-builder. It has been replaced with Storybook.
- Widget and theme manifest
supportedLocalesis changed to
polished.getValueAndUnit(value)is changed to
- The render callback function is changed to
(ds: DataSource, info: IMDataSourceInfo, query: QueryParams): React.ReactNode.
labelis renamed to
dataSourceJsonis renamed to
layerDefinitionis named to
- Entries in
jimu-uihave been refactored. Some entries are moved to the
advancedfolder. Below are the entry details:
- These components are removed:
CardImgOverlay, CardGroup, CardLink, CardSubtitle, CardText, and CardTitle.
Tabcomponent needs two new props:
popperOptionsprop and added two new props:
strategy: Defines the positioning strategy to use. By default, it is
absolute, if your reference element is in a fixed container, use the
onFirstUpdate: Invoked when a popper is positioned the first time.
containerprop. The current behavior is the following: if the
disablePortalproperty is false, then the dom of the popper will be appended to the body by
ReactDOM.createPortal. Otherwise, the dom of the popper will be rendered under its parent node.
toggleClassis renamed to
- The properties
appendTo(string)is changed to
appendToBodyis true, the dom of the
DropdownMenuwill be appended to the body by
ReactDOM.createPortal. Otherwise, the dom of
DropdownMenuwill be rendered under its parent node.
- The properties
onSelectare replaced by
SelectedDataSourceJsonis removed, replaced by
selectedDataSourceIdsis changed to
closeDataSourceListOnSelectis renamed to
- The type of parameters for
disableRemovehas been changed to
- Removed sort and filter related props.
onSelectis changed to
showDialogis renamed to
- These theme variables have changes:
Color, Dropdown, Slider, Pagination.
- Entries in