Clarification requested for "open in dialog" functionality: How do we suppress the "close dialog" icon?

Certified Lead Developer

I'm experimenting with turning certain Related Actions / Record Actions into the new(ly revived) pop-up dialog.  To be clear, I love that this functionality is back and that it's now optional, in a pretty flexible manner, and especially that it's configurable per each individual use of the Record Action component.

My apparent issue: no matter what I have tried so far, the dialog will render with an "X" icon in the upper right corner of the form, which causes the dialog to instantly close without any confirmation.  This seems to be the case regardless of whether the process is using a start form, or a regular User Input Task, either configured as a Quick Task or using the regular configuration.  If there is a configuration that affects this, it has thus far eluded me.

Screenshot:

This opens up some particular, potentially severe issues.

  • In a "strictly sites" based configuration, which I'm currently working under, if a user has launched a process instance using a User Input Task, and they use the "close" icon to close out of the interface (regardless of whatever buttons the designer has provided), the process instance will then be orphaned in the background as the user has no particular way of navigating back to that task unless special measures have been taken to expose Tempo tasks to users of the site (which we have no plans to do, in our project at least).
  • If the user has entered some amount of data on the form (either a start form or a user input task), it can be fairly destructive if the form is allowed to be closed without confirmation, accidentally or otherwise.  Yet the "X" icon causes the task/form to be closed, without saving, immediately, regardless of whether any amount of data has been entered.  Designers should be able to force users to only be able to close a dialog via a "Cancel Button" click or similar, where we can conditionally require last-minute confirmation as to whether the user really wants to dump the contents of that form they just spent 10 minutes filling out.
  • Probably more that I'm not thinking of yet...

Can anyone from Appian confirm or comment on whether this behavior is intended?  My expectation would be that there be some by-task and/or by-form configurability for this behavior, or at least that there be documented workarounds for ways to suppress it when needed.

  Discussion posts and replies are publicly visible

  • The 'Close Dialog' icon is present for all dialogs. We are aware of your concern regarding orphaned tasks since this can present an issue and does require workaround such as an exception timer. For now, Dialogs should appear mostly for start forms since they are encouraged when creating processes. Similar to leaving a browser tab, if rule inputs mapped to process variables have changed, the 'dirty flag' validation for a page will be thrown to prevent users from losing data. I recommend opening a support case to have an engineer submit a specific use case on your behalf.

  • 0
    Certified Lead Developer
    in reply to Danny Verb
    the 'dirty flag' validation for a page will be thrown

    Upon double-checking, you're right - what threw me off is that this doesn't happen when viewing the dialog from the interface designer (i.e. when editing the form that calls the ensuing dialog).  But it works as expected when using it live from a site, etc.  That, at least, is slightly better than what I was fearing.