Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
I want to create a custom UI where all my actions are displayed as styled buttons using a!buttonWidget, but still open the native record action dialog (start form, etc.) the way a!recordActionField does. Currently, a!recordActionField works fine for triggering the action and opening the dialog, but it doesn’t give me the same level of styling flexibility as a!buttonWidget. I tried using a!startProcess() inside the saveInto of a button, but that just runs the process silently without opening the dialog. Is there any way to call a record action directly from a button widget (and open its dialog), or is a!recordActionField the only supported method?
a!buttonWidget
a!recordActionField
a!startProcess()
saveInto
Discussion posts and replies are publicly visible
You cannot directly trigger a record action dialog from a!buttonWidget.a!recordActionField is currently the only supported way to trigger record actions with their native dialog behavior. There's no function or method to invoke a record action dialog from a button's saveInto.I would recommend, Use a!recordActionField with its built-in styling parameters and wrap it strategically.
Thanks a lot for clarifying this , that makes sense. I noticed though that the other button in the same interface is actually using a button widget, so I’ll need to align the approach for consistency.
Use the record action field. In case you need all buttons to be primary, use a list of record actions field instead of a single field with multiple actions.
Thanks, understood. One thing I realized is that the other button works differently, it doesn’t open a dialog but instead toggles a grid and extra controls on the same page (using showWhen and a!startProcess for submit/cancel). The new action, however, needs to be a pop-out since it’s not related to the grid, just another functionaility that the business request.