Data Collection Component
|
Data warehouse trend reports now show only the final data for each day
In the past, trend reports such as burndown reports and Cumulative Value Flow diagrams showed multiple data points for the same day.
Now, the report shows only the last data point. This way, if an ETL job fails so there's only partial data and the administrator has to rerun the job, the subsequent run ensures that the report has the correct cumulative data for the day.
|
Lifecycle Query Engine
|
Administrators can now easily access the logs
You can now download the Lifecycle Query Engine logs from the Advanced Properties administration page at https:<host_name>:<port>/lqe/web/admin/advanced. The settings in the install_dir/server/conf/lqe/log4j.properties file determine which logs are available.
|
|
Validate the index against TRS feeds
If you don’t find the right artifacts in your reports, you can use the new LQE validation, which compares the current TRS feed with the index. The validation process finds missing or extra artifacts but doesn't look at the content of the artifacts. The time required for validation depends on the size of the index.
To start validation, go to the Edit Data Source page. You can find the list of missing and extra artifacts in the lqe.log file after the validation has finished. However, if you see a discrepancy in the content of an artifact in a report, consider reindexing.
Note: This version of LQE introduces a new partition that is used for validation and shortens reindexing. When you first start LQE, a migration task creates the new partition. This process might take some time.
Image of the Validate button on the Edit Data Source page:
|
Report Builder
|
Group conditions to exclude data from a report
When you define the conditions for a report, you now have more flexibility to define exact conditions of what to exclude. You can now negate a grouped condition by using the AND NOT or OR NOT options. For example, you can specify that all items must match one group of conditions but not another group of conditions.
The AND NOT operation is the negation of the AND group. That is, if a group has three conditions named A, B and C, the AND NOT operation is "NOT (A AND B AND C)." The name of the AND NOT operation is "Not all match."
Similarly, the OR NOT operation is the negation of the OR group. That is, if a group has three conditions named A, B and C, the OR NOT operation is "NOT (A OR B OR C)." The name of the OR NOT operation is "None of them match."
In addition, the Conditions section in the My Choices pane at the right now shows the logical operators and the group structures of the conditions.
Image of the grouped conditions:
|
|
Names at both ends of an RM relationship can now be the same
Report Builder now allows the names at both ends of a Requirements Management (RM) relationship to be the same. When this situation occurs, only one end is shown in the relationship picker. The generated query checks both ends of the relationship for a matching name.
|