Let’s examine the “Card” widget used in the portal to present the core data of an item like a support ticket. As a matter of fact, the “Card” itself is merely used for design purposes, just like the “Columns” widget. The relevant pieces of data are rendered by a “Data Label” and a “Data Icon” widget inside the card. Both display an attribute from the “Data Group” widget’s “Ticket” context, “Keyword” (which actually is the ticket title) and the ticket “Type”, respectively.
You can of course use as many “Data Label” widgets as you need to display further content from the attributes available in the data context, like it’s done on the “Quotes” and “Orders” pages, for example.
Did you notice that list pages like these don’t have a “Data Group” widget for setting the data context? This is because the context originates from the pages themselves. It can be specified in their respective properties, and the items from this context can then be rendered using a “Data” widget that renders them one after the other.