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.
we have a collapsable grid whose individual cells contain dynamic links. Assume this grid takes up the entirety of screen. Upon clicking the dynamic link 3 variables are saved (local!showTransactions, local!accountEntityCode, and local!transactionAccPer).
Another interface loads below the grid when local!showTransactions = True.
However upon clicking the dynamic link value, there is no indication of this newly rendered interface. The current grid takes up the entire screen. We need some way to notify the user of the new interface rendered below. Ideally, when the user clicks on the hyperlink, it will jump to the section what was loaded below.
What we want to avoid using: recordLinks and startProcessLinks cause major slowdowns compared to dynamicLinks when generating the linked values of the collapsable grid. Dynamic Links are preffered. Any recommendations?
Discussion posts and replies are publicly visible
That's the issue with dynamic interfaces. Did you consider to display that collapsible section somewhere else?
Do you mean like in another tab? The modal and new tab are process heavy and very slow.
Any chance you can hide or at least majorly collapse the top grid when the bottom part is shown?
jenniferm0002 said:The modal and new tab are process heavy and very slow.
Not sure what you mean with this?
I think more about using a fixed size card layout which then would show a scroll bar if the content is longer. Or show that data left or right, instead of the form flow.
https://app.screencast.com/agKBwRNs3bd2V I've added a sample grid view to give you a better visual. The user is able to drillldown 4 levels and on the last level there's a link that provides a more details list of data. When the user clicks on the hyperlink, I want to system to jump to a section below with the list data. Because, we are dealing with calculated fields, generating a modal and tab have performance issues.
Here's a sample view of what the data looks like in the grid.
Not sure how to help you with this UI.
IMHO this feels like you try or have to replicate an existing app and it's specific UX. I typically try to think to rethink the user experience. Not because of any kind of "limitations" in Appian, but because bad UX in one tool, stays bad UX in the other tool.