The following major characteristics apply to all Advanced Reporting domains. See the descriptions of the individual domains for information that is domain-specific.
- Object Domains. Domains are provided for the most frequently used objects, including the new product investment objects (NPIOs), such as Ideas and Applications. In each domain, you can see only the product data that you have permission to view.
When viewing a domain in the ad hoc editor, the Fields section of the left panel lists all field properties (such as Investment names, OBS, text fields, and dates). The Measures section of the left panel lists all numeric amounts that are related to the fields (such as hours and costs). The items in Measures are fields for which you can do mathematical calculations.
- Internal IDs. Each domain contains an Internal ID set. You use internal IDs for building dashboards. Internal IDs are primarily used as filters by report developers and dashboard developers. These IDs, which are not used in ad hoc views, are the same across all domains. You can map these IDs to input controls and you can use them for filtering on dashboards.
Internal IDs are related to objects, not domains. If Investment data exists in multiple domains, the same Investment key is available in each domain.
Note: Dashboards are not provided with CA Clarity PPM. See the Jaspersoft documentation for information about how to build dashboards.
- Custom Folder. The Custom folder appears in a domain if you have custom fields or objects (related to the domain objects) that are Data Warehouse enabled. To verify that your custom fields and objects are Data Warehouse enabled, see your administrator. The Custom folders also include add-in fields. The Custom folder always appears as the first set under each object (after the list of object fields). If you have multiple objects in a domain, the Custom folder appears under each object folder. For example, the Team object includes its own custom team fields in a Custom folder under the Team folder.
If you add custom fields to an object (or if you install an add-in with custom fields) and the fields are Data Warehouse enabled, custom sets are created in the corresponding domains. The custom fields are included in the Custom sets under the related object.
Note: If a custom object or subobject has a lookup attribute, the key for it is included in the Internal IDs folder under the Custom folder.
- Period Type. When you select period types, select the same period type for both Fields (top of left panel on Advanced Reporting page) and Measures (bottom of left panel). Selecting different period types for Fields and Measures can produce unexpected results.
- Domain Sets. Domains are organized into sets and field items. The sets act like folders that you can expand to view the field items. Some examples of sets are the General and the OBS sets.
- Domain Security. You have access to specific domains based on your role. When you open Advanced Reporting, you see only the domains that you can access. However, you may not have access to all data in the domains that you can access. When you view a domain that you can access, you see all object sets and fields in that domain. However, the data that appears for the objects and fields depends on your role.
- Date Fields. Most of the dates in the domains are business dates that are displayed without time stamps and time zone conversions. The exceptions are the system dates, which display date and time and have time zone conversions applied to them. The system dates include Created Date, Last Updated Date, and Warehouse Updated Date.
- PMO Accelerator Fields. The PMO Accelerator fields are dynamically included in the domains (similar to custom attributes). However, the internal IDs of the PMO Accelerator fields are renamed when they are included in the Data Warehouse and the domains. The renaming of the internal IDs occurs only for PMO Accelerator fields. All other add-in fields have the same behavior as the custom attributes.
