Interactive Tooltip Requirement for Read-Only Grid

Hi everyone,

We have a UI requirement involving a read-only data grid. The grid displays values such as student names. When a user hovers over a grid cell, we want to show a clickable tooltip containing a list of related items. Each item in the tooltip should be clickable, and clicking on it should open a dialog box with detailed information.

Example Scenario:

  • The grid displays student names.
  • On hovering over a student name, a tooltip appears showing a list of mark sheets by year.
  • Clicking on a specific year opens a dialog box displaying that year's mark sheet.

Looking for suggestions or best practices on how to implement this kind of interactive tooltip behavior. Has anyone tackled something similar or used a library/component that supports this?

Something like: 

But the marksheet should be a Dialog Box that is associated with a record action.

Thanks in advance!

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    In addition to what Stefan supplied, I would add that using the RichTextDisplayField, it is fortunately trivially easy to add arbitrary (plain) mouse-over text to any field, in a dynamic manner (i.e. changeable to any extent that you can apply expressionable logic to it), onto any cell in a grid. 

    And in recent Appian versions, this mouseover text (with no mention in the updates or the documentation, which is crazy since it's a GOOD change) started allowing line-breaks (simply use "char(10)" anywhere you want a line break), making for many more formatting options.

    All that said, of course, there is no advanced formatting (not even rich text, sadly), no clickability (this would get very complicated, to be fair), and still no pop-up prompts or pop-up actions other than record actions (which is, in my opinion, overly limiting). 

    On that note: my 2 old feature requests are still outstanding and, sadly, still being ignored: 1) adding a pop-up confirmation on Dynamic Links (and perhaps similar things) like we can do with ButtonWidgets, and 2) adding a "pop-up" target to Start Process Links, allowing us to start arbitrary actions in a pop-up and not just Record Actions, since not every use case is able to be shoehorned into a Record Action (even though they want us to).

    I also have a lower priority feature request floating around out there somewhere, which is for them to improve "caption" and "tooltip" parameters to accept "a!richTextItem()" objects instead of just plaintext, allowing at least basic formatting.  But again, not holding my breath on that one.

  • I really appreciate your feature suggestions—they’re insightful and clearly well thought out. It would be great if there were a way to vote on them, as I can envision several scenarios where these features would add significant value to the application we're building.

  • +1
    Certified Lead Developer
    in reply to sanjuktab2257
    It would be great if there were a way to vote on them

    The only "official" way is to create threads here and hope people see them (and then hope Appian sees them).  Not very effective.  I've long dreamed of creating a website where vetted feature requests could be added and then devs could pledge "bounties" for certain things being added (as bonuses payable to whatever Appian engineer and/or team is responsible for a feature making it into a main version), but sadly I don't have the time or expertise to accomplish such a thing as far as I know, and I haven't had much success yet locating a pre-built platform to facilitate it.

Reply
  • +1
    Certified Lead Developer
    in reply to sanjuktab2257
    It would be great if there were a way to vote on them

    The only "official" way is to create threads here and hope people see them (and then hope Appian sees them).  Not very effective.  I've long dreamed of creating a website where vetted feature requests could be added and then devs could pledge "bounties" for certain things being added (as bonuses payable to whatever Appian engineer and/or team is responsible for a feature making it into a main version), but sadly I don't have the time or expertise to accomplish such a thing as far as I know, and I haven't had much success yet locating a pre-built platform to facilitate it.

Children
No Data