Aggregation UTA

Revision as of 12:07, 3 October 2013 by Arthur Lathrop (talk | contribs) (Create Templates/Statuses and Fields)

Revision as of 12:07, 3 October 2013 by Arthur Lathrop (talk | contribs) (Create Templates/Statuses and Fields)

An Aggregation UTA facilitates creating reports that span multiple related Universal Tracking Applications™ (UTAs) by defining the association between equivalent fields in each UTA.

Contents

Important aspects of the Aggregation UTA

  • The information residing in the Aggregation UTA is a copy of the information from the source UTAs.
  • If information in the Aggregation UTA is modified, it does not modify the information in the source UTAs.
  • The information in the Aggregation UTA is saved as text.
  • Although the fields may be named differently in each UTA, they can map to the same field in the Aggregation UTA.

Configuration Steps for an Aggregation UTA

Create Templates/Statuses and Fields

  • Determine the statuses, templates and common fields from both UTAs that you wish to include in the report. Create matching statuses, templates and common fields in the Aggregation UTA in the usual manner (they needn't have the same names as the original statuses, templates or fields). The fields can be either standard fields or custom fields.

Map Types and Statuses

In the UTA Settings page of the Aggregation UTA, click on the link for Aggregation Settings.