Understanding the parent panel types

The following are the different panel types offered in Panel Designer:

  • Contact – Associates the table data with a specific contact. These are the panels you put on user account pages to display data that is specific to each contact.

    • For Contact panels, an ID is automatically generated for the business object that represents the panel data source. The ID is a unique value used to join the business object to other panel data sources and business objects in IQA. It is also used as the iMIS ID for linking in IQA.

    Note: When using the Bill to ID property, it is recommended you use CsContact.BillToId instead of CsNameFin.Bt Id.

  • Event - Associates the table data with a specific event. Panels can include properties for resources, sponsors, hotels/venues information, or any data you want a value list for. Panels associated with events results in creating panel sources such as tables and business objects that have a column for EventKey. An EventKey is a unique value used to join a business object to other panel data sources and business objects in IQA that represent events. For event panels, an EventKey is automatically generated for the business object that represents the panel data source.

    • All other properties and single and multi-instance panels can be used when created event-based panels.

    Note: When using the Bill to ID property, it is recommended you use CsContact.BillToId instead of CsNameFin.Bt ID.

  • Invoice - Associates the table data with the invoice data. Panels may include any custom properties, excluding File upload properties. The InvoiceId property is used to uniquely identify the panel data for an invoice.
  • Standalone - Does not associate table data with a specific contact. Standalone panels are multi-instance only and can be used anywhere in iMIS. These panels are useful for anonymously tracking information or creating a multi-instance form. See Creating standalone panels for more information.

    • Note: Only staff users and system administrators can create, edit, view, and delete standalone panels. Public users cannot view standalone panels, and as a result, standalone panels should not be added to any public-facing content records.