Open a details interface from an action interface (i.e. User Input Task)

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

Parents
  • 0
    Certified Lead Developer

    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.

Reply
  • 0
    Certified Lead Developer

    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.

Children
No Data