How to make a process model user action open in modal

RE: How to make a process model user action open in modal

Harsha Sharma — Fri, 31 Oct 2025 17:28:15 GMT

I had worked with a similar data structure earlier.
In my design First is a create action that stores formHeader and lineItems in database. In the interface I suggest you to make use of a wizard layout for this.
For further details, have a wizard with 2 steps - in 1st step have the user fill details for formHeader and store in respective record type variable. Then in step 2 of wizard provide a grid where user can fill lineItems and store in another variable of respective record type. Using relationships can complicate primary keys setting once you go into process hence two different rule inputs are easier during creation.

When user completes this form write the records in the process. Now use Update action for itemEvents. You can use paneLayout() here so that in left pane you can show lineItems in a read-only selection enabled grid. When user selects a row display form in right pane for user to enter itemEvents against selected lineItem. Using selection each lineItem can be releated to itemEvent entered for. Lastly when user submits write the itemEvents records.

RE: How to make a process model user action open in modal

Stefan Helzle — Fri, 31 Oct 2025 16:49:40 GMT

That second paragraph sounds like a good idea.

https://appian.rocks/2023/06/20/popup-windows-in-appian/

I use this pattern to create such complex UI.

RE: How to make a process model user action open in modal

Mike Schmitt — Fri, 31 Oct 2025 16:18:19 GMT

My old fallback for adding or editing line-items where they have complex requirements or validations is to simply put the item list in a read-only grid, and make the user click an "edit" control on the grid which will then show the expanded items for just that row in a little section below the grid, complete with its own buttons including "save" and "cancel".

I'm not sure what-all you're trying to do with "form headers" or whatever, but following my approach is usually at least one path to success. Sadly there isn't a way to arbitrarily open pop-up windows/tasks/controls, the sole exception being a Record Action set to open in a window (which rarely suits the use case at hand).