Overview
Dialogs allow a user to quickly view supplementary details as an overlay and then return to the primary UI. This is particularly useful if the user has made selections or entered data into the primary UI which they wish not to lose by navigating away.
SAIL Dialogs is part of the Appian App Accelerators (A3) suite.
The SAIL Dialogs application gives you the ability to drop links into your UIs which open a dialog. The SAIL interface rendered in the dialog is of your choosing. The link itself will be provide dynamic inputs to the dialog interface based on the context of the link.
Using the framework is 2 simple steps:
I'm a little confused by your screengrabs. Is the View Details the dialog example? Do you have any recent and or more detailed examples of your implementation? Thanks!!
@souperbpm Yeah, engineer here building apps, because I like low-code - NOT a proficient writer of technical documentation!
The following image is just an example showing that the dialog link can be rendered inline in an interface and looks natural. In this example it's rendered using ICON style (no link text) and placed in a grid.
This image is showing how you might add those dialog opening links or icons to an interface. For each one you call the A3_D_dialogLink rule. The key is a reference to which interface to show in the dialog - more on this below. And as shown here, you can pass some inputs to the dialog. Lines 1 and 10 are just indicating that you would of course have your application specific SAIL surrounding this link.
This image shows where the mapping from key (used above) to dialog interface is done. So you register an interface here, then you use the A3_D_dialogLink rule to embed links where you like. There are more detailed instructions about the expected contract in the README object within the app.
I hope this helps clarify, please let me know how else I can help.