Quickviews

A quickview is a read-only UI element which allows the user, at runtime, to view additional information (not displayed on the current screen) about an object without having to navigate to other screens to obtain the information. Like a tooltip, a quickview appears (and disappears) on the UI during a mouse-over action by the user.

The following types of quickview exist:

• Thing Quickview

  This is used to display information relating to a 'thing' (a business object for example). It is implemented using the Web Dynpro component FPM_QUICKVIEW_THING.

• Dataset Quickview

  This is used to display information relating to a dataset. It is implemented using the Web Dynpro component FPM_QUICKVIEW_DATASET.

• Image Quickview

  This is used to display an image related to the field it is assigned to. It is implemented using the Web Dynpro component FPM_QUICKVIEW_IMAGE.

A quickview can be assigned to a particular element of a generic UI building block (GUIBB) component inside an FPM application. For example, a quickview could be assigned to a particular column in a table (implemented using a list component). As the user hovers the mouse over the rows in this column, the same quickview is displayed for each row, but the data inside the quickview changes.

The information displayed in a quickview at runtime is determined both by the feeder class assigned to the configuration of the Web Dynpro components mentioned above, and by the settings inside the FPM configuration editor, FLUID.

Quickviews can be exchanged with other quickviews dynamically. Therefore, quickviews that were not assigned to a particular GUIBB at configuration may still appear on that GUIBB at runtime.

The following screenshot shows an example of what a quickview (in this example, a thing quickview) might look like at runtime:

In this example, the quickview is triggered when the user hovers the mouse over a hyperlink.

As the screenshot illustrates, a quickview may contain the following parts:

• Quickview Title

  Static; this title remains the same for each instance of the thing. It represents the type of thing and is independent of the instance title.

• Instance Title

  Dynamic; supplied by the feeder class assigned to the quickview configuration, and changes for each instance of the thing.

• Icon

  Optional.

  Can be static or dynamic. Icons may be configured statically (the same icon is displayed at runtime for all instances of a thing) in FLUID or the feeder class may provide the icon(s) at runtime.

• Attributes

  The list of attributes available is determined by the field catalog of the relevant feeder class.

You can create, configure, and assign a quickview using the Quickview Panel in FLUID. FPM also provides a fast-track method for image quickviews.

Once a quickview is configured, it can be assigned to an individual element of a GUIBB; the Quickview ID is entered in the Display Type Dependent Properties section in the Attributes section of an individual element inside the <GUIBB> Schema panel in FLUID.

The fields available in the General Settings panel of the quickview component are component-dependent. Amongst others, are the following:

• Quickview Title

  This can be changed dynamically at runtime.

• Image

  If the image is dynamically created by the feeder class, the Image (Static) field is not available in FLUID.

You can edit the attributes' text and sequence, and, depending on the quickview type, also add a launchpad (display type Link to Action) to an attribute.

Each attribute has one of the following display types: Text View, Image, Link to URL, and Link to Action, meaning that the information displayed here might be in the form of an image or text, a hyperlink, or it might result in an action. You can change the display type to suit your requirements.