Getting started with ArcGIS Experience Builder

提示
19th August 2021

ArcGIS Experience Builder现在已经作为产品漂浮了一段时间了,其长长的惊人功能和他们创造的无尽可能性。当您将头缠住时,这是一个很棒的产品,但这也许也是如此令人生畏的原因。许多方向要去,但是从哪里开始?好吧,我在这里打破了那个障碍,并希望您鼓励您将脚趾浸入创造体验的激动人心的世界中。

AND… if you’ve really caught the Experience Builder bug, you can watch our recent webinarherefor an extended version of all the below topics.

它是什么和它住在哪儿?

The first thing to address is, what实际上is Experience Builder? If you’ve seen example ‘experiences’ (the term used for Experience Builder outputs), you’ll probably note they look a lot like other parts of the ArcGIS System… Is it a Storymap? Or even a Hub page? Maybe an embedded Ops Dashboard or Web App Builder? Well the short answer is, Experience Builder takes all those amazing features and puts them into a single location. The intention is not to replace these other products, but provide opportunities for users to combine the best features from across the ArcGIS System and create an experience with them.

The benefit of designing an experience that might act like another Esri product, is the ability to completely control each element on your page in terms of size, position and functionality. Experience Builder is built with Javascript 4.x., which means full flexibility on resizing elements, all that drag and drop goodness and the ability to use maps/apps built from the new Map Viewer (also built with JavaScript 4.x).

drag and drop functionality

最后介绍ductory point I want to mention is surrounding the commonly asked question ‘will this replace Web App Builder?’. No it won’t. The two products will continue to co-exist, however with the previously mentioned Javascript 4.x build, this will make Experience Builder a preferred option as Esri technology evolves and moves towards JavaScript 4.x (i.e. the new map viewer).

那么从哪里开始呢?

Of course, you could start from scratch. You can build your experience from a blank canvas and design it exactly how you like it, but I imagine you wouldn’t be reading this blog if you were that kind of person. So for me, the best place to start istemplates.有20多个模板可供选择,您可以选择合适的ESRI模板作为起点的场所,然后从编辑已经预先配置的体验开始。这种方法使让Esri在页面结构上进行繁重的工作变得容易得多,并让您将所有创造力集中在重要的东西上,例如小部件和颜色。您还可以在ArcGIS Online上创建,共享和使用模板,当他们想通过一致的品牌设计体验时,这对您的组织中的其他模板很方便。即使是在公司的徽标中添加和调整颜色的简单性也可能使该应用程序感觉像您自己一样。

Using an Esri UK template

Widgets

At the heart of Experience Builder are widgets. They are fundamental to making your experience come alive with functionality and I want to give you a quick overview of how they’re configured. All widgets are split into two categories, Basic and Layout widgets. Basic widgets resemble those we’ve seen on Web AppBuilder, the widgets that create certain triggers such as exporting your map or filtering the data. Layout triggers have a different purpose and are there to help structure your page. They allow you to create things like panels or columns/rows for your basic widgets to sit on top of.

Once you’ve selected your widget, explore the configuration settings which present you with three configuration elements:

  • Contentis what data source your widget will look to interact with.

Content

  • Styleis all about the aesthetic, selecting colours, style and even animation options.

Style

  • Actionis unsurprisingly, the ‘what is going to happen’ section of a widget. You can define the trigger of your widget i.e. zoom into this extent or export as CSV.

Action

主题

主题s are a mechanism we’re starting to see across the ArcGIS system. They meet a growing demand for users to make their apps look exactly how they want. You might have seen how ArcGIS Storymaps takes theme customisation to a new level, That’s why the theme in Experience Builder allows you to customise the fonts, font sizes and colours of your experience, then share this far and wide across your organisation.

Publishing

Once you’re happy with your created experience, sharing it works in a similar model to other parts of the ArcGIS system, such as in ArcGIS Storymaps. You design your experience in the draft status, then once it’s ready you发布。You can then share this either publicly or within your organisation. At this point, you can continue to make edits in a sandbox type environment without the risk of editing the live version. Once you are happy with your changes, you canPublishthe changes to the live version. The url for the experience stays the same across any updates.

For me, these are the fundamental ‘getting started’ elements that I believe will give you a solid foundation to explore more of Experience Builder’s wonderful features. Starting with a template and a basic understanding of widgets will allow you to explore the builder with confidence, hopefully designing your ideal experience in the process. I hope you’ve found it useful!

提示