42. Issue: An unexpected error occurred while creating a query using a Grouped Bar Chart with Boolean types of data.
(Reference: 415069)
Resolution: Grouped Bar Charts now correctly display data when using any of the supported data types.
43. Issue: Drilling down into a chart, a user could see an unexpected error page if there was a null value in the returned
time field. (Reference: 413954, 419692)
Resolution: Chart drill-down now works as expected and no longer returns an error when drilling down into null time-
based reports.
44. Issue: Some international characters caused problems in the server log details page. (Reference: 411088)
Resolution: Log entries are now correctly formatted prior to being written to the server task log.
Issues from the Patch 2 release of the software that are resolved in this release are listed below.
1. Issue: When accessing the “Systems/Client Tasks” tab of the ePolicy Orchestrator console, users without Administrator
rights receive the error “An unexpected Error has Occurred.” (Reference:360915, 400549)
Resolution: Users without Administrator rights can now access the “Systems/Client Tasks” tab.
2. Issue: The Product Catalog displayed hidden policy assignments. (Reference:359111)
Resolution: The Product Catalog no longer displays hidden policy assignments.
3. Issue: New DAT detection and installation scripts are available for inclusion in the Patch. (Reference:395895)
Resolution: This Patch includes current DAT detection and installation scripts.
4. Issue: On the Actions page, the Schedule Pull server task incorrectly invoked the “Purge Server Task Log” action.
(Reference:358624)
Resolution: The Schedule Pull server task now correctly invokes the “Repository Pull” option.
5. Issue: Distributed repositories from different ePolicy Orchestrator servers could not be used as a source repository in
another ePolicy Orchestrator server. The second ePolicy Orchestrator server failed to validate the package even after
importing the source repository’s public key. (Reference:375338)
Resolution: Distributed repositories from a different ePolicy Orchestrator server can now be used as source repositories
for other ePolicy Orchestrator servers.
6. Issue: ePolicy Orchestrator extensions did not display their build number as part of their version on the
Configuration/Extensions tab. (Reference:382248)
Resolution: ePolicy Orchestrator extensions now display their product build number as part of their version number in
the Configuration/Extensions tab.
7. Issue: When an incompatible query chart type or result type was used for the Generate Compliance Event task, an error
message indicated that a query of chart type was needed. The correct required query type is a Boolean Pie Chart.
(Reference:386081)
Resolution: When an incompatible query type is used for the Generate Compliance Event task, the following error
message is now displayed: “Validation error: Invalid input from the Run Query command. The query must be of both
Managed Systems result type and Boolean pie chart type.”
8. Issue: An agent package could fail to rebuild when one of the package’s files had been updated. (Reference:391143)
Resolution: An agent package is now rebuilt for agents even after files in the package have been updated.
9. Issue: There is no way to purge the Rollup Compliance, Rollup Systems, and Compliance History tables.
(Reference:364364)
