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:
Yes exactly as you're implying, there is a limit. It is after all an identifier. This app is a workaround and as such naturally does something odd like use an identifier field for a payload and as such incurs a limitation.
The dialogLink rule does throw a friendly validation error to advise you on this: "Dialog inputs are limited to 2000 characters when serialized as JSON. The dialog inputs currently have a serialized length of 2001 characters. Please restructure your inputs to be more brief. The intent is for the inputs to include only identifiers which will be used by the dialog's UI to query any needed data."
CDT I have already updated to support 50k characters for input and key fields
Hi Team, Is there any limit for data that we can send though the identifier in record action field. Whenever I am sending more that some thousand characters it is not working , have you faced this issue?
Loredana and I caught up. This issue appears to be an Appian platform one which is reported elsewhere and in some cases prevents valid process models from importing or being saved. The issue is in the early stages of investigation with no confirmed root cause. It can be tracked as support case 564775.
Loredana Parasiliti oof, sorry to hear about the trouble. I will look into this, try to reproduce the issue, and get back to you in the next few days.
Hello, some months ago I tried to import the application in a 21.3 Appian instance without success (same error about invalid process model as reported by the below thread).
I've tried again to import the application in the same environment, now migrated to 22.1, but I got the same error
Problems (1):processModel 0000e504-e427-8000-c431-7f0000014e7a "A3_D Supporting Process Model": An error occurred while creating processModel [uuid=0000e504-e427-8000-c431-7f0000014e7a]: com.appiancorp.process.validation.ValidationException: Process Model is not valid. (APNX-1-4071-007)
Cascading Problems (3):recordType 0dc1e5f0-33fd-49bf-afda-4527c86a9a03 "A3_D Supporting Record Type": The recordType [id= uuid=0dc1e5f0-33fd-49bf-afda-4527c86a9a03] was not imported because a required precedent is missing: processModel [uuid=0000e504-e427-8000-c431-7f0000014e7a location=Record Actions > Related Actions ["viewL"] > Related Action Process Model] cannot be found. (APNX-1-4070-001) (APNX-1-4071-006)content _a-0000e4fe-525e-8000-9c32-011c48011c48_23969849 "A3_D_dialogLink": The content [id= uuid=_a-0000e4fe-525e-8000-9c32-011c48011c48_23969849] was not imported because a required precedent is missing: recordType [uuid=0dc1e5f0-33fd-49bf-afda-4527c86a9a03 location=Interface Definition] cannot be found. (APNX-1-4070-001) (APNX-1-4071-006)content _a-0000e52c-8121-8000-9c39-011c48011c48_24237536 "A3_D_demoInterface": The content [id= uuid=_a-0000e52c-8121-8000-9c39-011c48011c48_24237536] was not imported because a required precedent is missing: content [uuid=_a-0000e4fe-525e-8000-9c32-011c48011c48_23969849 location=Interface Definition] cannot be found. (APNX-1-4070-001) (APNX-1-4071-006)
Success (3):content _a-0000e4fe-525e-8000-9c32-011c48011c48_23969149 272951 "A3_D_dialogRegistration"content _a-0000e525-d042-8000-9c37-011c48011c48_24218044 272952 "A3_D_README"application _a-0000e525-d042-8000-9c37-011c48011c48_24216962 217973 "A3 Dialogs"
Not Changed (18):...
Any suggestion to successfully import the application?
Regards,
Loredana
@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.
Ok got it. I just posted a request for any other visual examples you might be able to provide. Thanks as always for your responses!!
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!!
sba2018 I tried a few things and was unable to reproduce any errors on a 21.2 GA site or a 21.2 site off the latest hotfix. Are there any errors in the appserver log at the time of import? If that's not an avenue you can pursue, please create a support case and mention me. I'd like to get this working for you.