Fixed bugs

The vSphere Perf Collector was unable to collect data for some performance counters because it defaulted to counters that required a Statistics Level higher than commonly used.

You can now use the rollupType property in a perf profile to specify a counter that requires a lower Statistics Level. This new property is required in all perf profiles.

You could not import COGS resources from CC Records using the ImportNewResources transform processor.

When importing resources, anytime an existing resource was updated the group name specified in the import record was applied, causing resources to move unexpectedly in the Cloud Cruiser Portal.

The default behavior is now to ignore a group name for an existing resource, but you can override this. With the ccimport command or the ImportTasklet batch tasklet, use the updateGroupFlag parameter or property. With the ImportNewResources transform processor, use the updateGroupTitle property.

A significant issue slowed the loading of summary data into the database from the charge step.

When the application server was stopped while users were logged in, their login credentials were written to a log file in plain text.

Windows Azure Pack subscriptions that began on a date later than the date for which they were collected were dropped, causing any usage against these subscriptions to also be dropped.

When the enableMissingFeedSupport property in the assembly step of a batch job was set to true, no warning was generated for missing records until the missingDaysLimit was reached.

When using a ResourceFamily to disable proration for one or more resources in the charge step of a batch job, the keyIdentifiers you specified were ignored. This resulted in extra charges being loaded for the resources in question.

When the Excel collector used a feed configuration with the header property set to true and one of the cells in the header row of the input file was empty, collection failed.

When the Excel collector encountered a row in an input file where a cell mapped to either the usage start or end time was empty, collection failed.

When you logged out while viewing a window visible only to users with the Admin role and then logged in as a user without that role, you received an Internal Client Error message and the navigation menu was hidden.

In the Job Loads and Alert Status windows, when working with date range filters the Clear button sometimes would not work.

When you called the REST API method http://<ccServerURL>/rest/v1/reports and omitted the userGroupName parameter, the resulting error message was not helpful.

When you attempted to import a translation table from a CSV file whose size was larger than allowed, the error message you received did not explain the reason for the failed import.

If you specified an invalid targetLevel value in the charge step of a batch job, the job failed with a stack trace instead of giving a useful error message.

If you set an account level filter in the Customers window, then navigate to another window in the Cloud Cruiser Portal and return to Customers, the filter appears set but is not applied to the displayed list of customers.

When you clicked an item in the main navigation, there was a delay before the menu for that item appeared.