What the UI Control Changes look like in the Report Runtime Version

This is the fourth topic in the tutorial about configuring UI controls.

Editing the properties of UI controls determines what the user will see at runtime.

The image below shows two views of the Availability Comparison Template. On the left is the Editing view. This is what you see when editing the UI control parameters. On the right is the Runtime view. This is what the user sees at run-time when they are setting up the report to run.

When you are in Custom Report Management:

• You can reorder the prompts to determine how they will display at runtime.
  When creating custom reports, you will need to edit the UI controls so that the reporting period and start and end date parameters appear at the top of the list in the following order:

  • Period (for those reports that require this parameter)
  • Start Date
  • End Date

  If this order is not maintained, the report will not generate.

• You can provide the hints that will display for the user.
• You can set up data dependency on UI controls, so that the selection of one UI control parameter populates another. For more information, refer to What the UI Control Changes look like in the Report Runtime Version.
• You can hide some items and make their visibility dependent on the selection of another item. For more information, refer to What the UI Control Changes look like in the Report Runtime Version.
• You can assign two or more parameters to a validation group. This allows a user to select one item from any of the group to populate a list, or forces the user to make a selection from one of a group. For more information, refer to What the UI Control Changes look like in the Report Runtime Version.
• You can provide visual separation of the UI at runtime by inserting a line across the UI screen.