Enabling data completeness check in Report Builder new user experience

Use data completeness check in Report Builder new user experience to verify whether a specific report has problems.

1. Open a report to edit it.
2. From the Filter the results dialog, select the Run data completeness check checkbox.
3. From the drop-down menu on the Configuration tab, select Find a configuration. Choose the domain, project area, component, and configuration, and then click Accept.
   

   Note: The Run data completeness check evaluates only the single configuration upon which the report is scoped.
4. To generate the report, click Run.
   The report is generated and displays information on skipped resources, missing resources, or resources with failed patches, if any.

   You can also view the information about number of data sources that are processing the change logs. If the message states that the LQE is processing the change logs, it implies that the data might be incomplete. Wait until the LQE completes the change log processing and is up to date.

   Note:

   • Skipped resources: The most common causes for skipped resources are internal server errors, socket timeout, authorization issues, and deleted resources that are skipped from the selected configurations.
   • Missing resources: Reports do not show the artifacts that you expect from the selected configurations.
   • Failed patches: If patch events are not applied, reports and queries on specific configurations might return incorrect results.

   To determine whether these conditions affect your report, go to the Query Statistics page. This page lists the URLs of all affected artifacts for the specific report. It also shows the LQE data providers, which you must review for further analysis.

   Note: For more information, see Reporting on data in configurations with Report Builder
5. Optional: Contact your system administrator to troubleshoot the following issues.
   1. For skipped artifacts, see Lifecycle Query Engine skips resources during indexing.
   2. For missing version artifacts, see Validating TRS feeds and the LQE index.
   3. For missing configurations, the user needs to identify the configurations that are missing. The global and local configurations are the most common missing configurations.
      The most likely reason for missing the global configuration is that it is archived. The user can investigate the reason for Global Configuration hierarchy to include a contribution from an archived Global Configuration.
      The most likely reason for missing the local configuration from Engineering Workflow Management SCM and Rhapsody® Model Manager is that such configurations are not explicitly published in the TRS. In Engineering Workflow Management SCM and Rhapsody Model Manager, configurations are only published in the TRS if the user explicitly adds or publishes them. It is done through the Engineering Workflow Management UI. If a handful of configurations are missing, that is a reasonable approach. However, if several configurations are missing, the collection of missing configurations must be added by using the Engineering Workflow Management SCM or Rhapsody Model Manager command.
      Note: The Report Builder does not give any specific guidance in this case. It can identify that one or more configurations are recursive contributions to the specified GC hierarchy and that they are missing along with the URIs of those configurations. However, it cannot determine the application names that own these missing configurations, or any other information.
      To find out the possibilities for better automation, you must liaise with the Engineering Workflow Management SCM and Rhapsody Model Manager teams. For more information on adding the configurations to TRS, Engineering Workflow Management SCM, or Rhapsody Model Manager, the Engineering Workflow Management or Rhapsody Model Manager administrator can refer to Publishing SCM configuration resources and publish.
   4. For missing selection artifacts, usually the action is same as the missing version artifacts.
   5. For failed patches, see Troubleshooting failed patches warnings.