The Web Flows Builder provides the tools to build out the UI for web experiences, which encompass everything from the structural layout of web apps to what Actions will be taken in response to user input. This is the Builder in which Web Flows are made out of Web Pages, and where Web Pages are made out of component Web Controls.
Like most Builders, the layout of the Web Flows Builder maps comfortably onto the general structure of the Studio: to the immediate right of the Builder Bar is the Tree, to the right of which is the Stage, to the right of which is the Inspector:
The Tree displays, at a high level, the various individual components that make up a web experience. At any given time, the Tree can display one of two tabs: Navigator or Controls. Toggle between the two by clicking the relevant tab at the top of the Tree.
Displays an expandable and collapsible breakdown of the various components that have been built out as part of a web experience.
Displays and expandable and collapsible breakdown Web Flows, Web Pages, and Web Controls. This section also provides the option to add additional components: clicking the '+' icon that appears when you run your mouse over a listed component provides the option to add a subcomponent that will be nested directly under said branch.
These components and subcomponents are structured as follows:
Web Flows- typically designed around a specific work flow.
Where you define the global layout of an application. It can be used to create a header or footer for web apps.
Contains the tools to create custom Web Controls that can be reused across Web Flows.
Because Web Controls can only be added to Web Pages (recall how the components of web experiences are nested), the Controls tab is only accessible when working within a Web Page or creating a header in Layouters.
Displays a visual representation of the aspect of the app being modified, making the impact of changes clear in real time. Exactly what is displayed in the Stage varies to better communicate the type of modifications being made. When examining a Web Flow, the Stage will display every Web Page within it. When examining a Web Page or a Web Control, only that Web Page will be displayed. When the Stage displays a single Web Page, clicking on an individual Web Control within the Stage opens up the interface to make edits to it in the Inspector. The following example shows how the interface in the Inspector changes as various Web Controls, two Labels and a Button, are clicked on:
Provides the tools to examine and modify the individual elements that make up an application as well as configure specific interactions. Precisely what those interactions are depends which element you're inspecting. For instance, the following example shows how the Inspector can be used to modify the text that appears in a Button:
To better reflect the functionality of the Inspector, its layout changes subtly even when being used to examine relatively similar things. Consider Web Controls: there are changes that can be made to some Web Controls but not others. For example, the Inspector appears differently when examining a Button as compared to a Label, in part because Buttons can be clicked, triggering actions, whereas Labels can't.
In general, there are three tabs that may appear in the Web Flows Builder Inspector: General, Actions, and Advanced. Not every element allows access each tab while being inspected, because different elements allow different modifications.
Contains the fundamental information associated with the element being inspected. This includes details about the element itself, relevant variables, and material concerning styling.
Under the Actions tab, you'll be able to access the Action Builder. This allows you to associate Action Chains with the any Events associating with the element you're inspecting.
As a rule of thumb, the Advanced tab provides the ability to inspect and edit any functionality that didn't fit neatly into the first two tabs. Most commonly, the Advanced tab is used to dictate when particular Web Controls should or should not be visible or functional. For a deeper dive into how this works and when you might want to leverage this feature, check out this document on creating dynamic forms based on user input.
Updated 2 months ago