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.
Scenario: A user opens a task and sees an actionable interface (they enter data, click submit, it goes back to the process model, etc). The interface displays several key pieces of information the user needs in order to complete the task. In addition, there is a button/link/widget on the interface that will open a second window with a lot more details regarding the context of this request. Both windows need to be open at the same time and the user can tab back and forth between the two in the browser (or set the two side-by-side using two browser windows) as they complete the user input task. The action interface has a dozen or two fields. The details interface has a couple three or four hundred pieces of information.
NOTE: There are no record types being used here. The details data is a large XML object that comes from an integration which will likely be placed into a similarly large, hierarchical CDT structure.
Question: How can I open the details interface from the user input task interface and pass it a context (e.g., some rule input value)?
Discussion posts and replies are publicly visible
The details interface displays read-only data.
Why not build a tabbed interface with an alternative side-by-side view?
I will give it a try and see if it passes muster with our user interface police.
Thank you.
Hmm.... If the side-by-side could be independently scrollable, that might be okay. As it is, if you need to scroll down to the 300th data element on one side, you have scrolled up the other side off the top edge of the browser.
What if you did something like put a fixed-height card in the read-only column? If you did that, you could force everything in that card to scroll without needing to affect the entire interface.
The one thought I have is, if you could figure out a way to shoehorn the "long list of details" data into a Read-Only Grid, you could use the feature where you define a sepcific height in the grid (forcing it to scroll vertically), confining the totality of the interface to around a page in length, even if the grid scrolls on for several pages worth of additional length. I don't immediately know of any other components where you could optionally enable independent scrolling within the same interface.
Edit: Peter beat me to it i guess - I forgot you can also force Cards to be fixed-height. That would probably work a bit more flexibly.
You and Mike had the same idea..... Is there a way to variably fix the height of the card? For example, some users display are set to lower resolution, some set to higher resolution. Ideally, I might want the card to consume 75% of the vertical space and scroll after that.
Ok, I tried it and it seems to work out well. I used EXTRA_TALL for the card height.
Thank you all for your suggestions.