Fixes And Enhancements

Code42 Public Cloud

Fixed rare issue in large environments where information could be missing from the beginning of the app.log file.

Improved error messaging when attempting to create a user with a username that is not an email address.

Fixed rare issue where CrashPlan for Small Business users were allowed to click Save more than once when updating expired billing information, which could result in duplicate payments. Please contact our Customer Champions​ if you believe you were billed more than once.

Security updates.

Administration Console

Improvements to accuracy of dashboard graphs and statistics.

User devices are now sorted alphabetically by device name in the User detail view.

In Organizations > Overview, the Backup column is now labeled Backup Devices.

From Organizations > Overview, clicking a value in the Backup Devices column now displays the list of devices for users in that organization.

Changes To Code42 API Resources See Upcoming Changes To The Code42 API for complete details about the specific changed and deprecated resources and parameters. Make sure to review your scripts, integrations, applications, and reports that utilize the Code42 API and make any necessary updates.

User Deactivation

Previously, deactivated users were unable to sign in, regardless of whether or not they were blocked. Now, users must be both deactivated and blocked to prevent them from being able to sign in. Deactivated users who are not blocked are now able to sign in.

As a result, the implications of deactivating and reactivating users directly via the API have changed. There is no impact to deactivation/reactivation performed via the administration console or via LDAP.

To preserve the previously expected behavior of preventing deactivated users from being able to sign in:

UserDeactivation now also defaults to executing the UserBlock resource.

A new parameter was added to UserDeactivation to control whether or not the UserBlock resource is also executed. By default, deactivating a user also blocks the user.

This new parameter also controls whether or not users are unblocked during reactivation. By default, reactivating a user also unblocks the user.

Fixes And Enhancements

The PIN query parameter of the GET method was removed from the QSFile resource. The PIN is now included in the header.

Multiple userUids can now be submitted to the AddressBookEntry resource, reducing the number of calls to the server needed for certain queries and management tasks.

Setting the incVolumes parameter of the Diagnostic resource to false no longer displays volume information.

The Cli resource now supports Cross-Origin Resource Sharing (CORS), securely enabling more flexible use of the API.

API Documentation Viewer Updates

The PlanEvent resource entry now specifies that queries that include a fileID or file path only provide results for file events. Shared link events are not included.

A summary was added for the Archive resource.

The Destination resource notes that the computerCount output value was renamed backupComputerCount.

Known Issues

In the administration console, Enable Balancing incorrectly appears as an option in the action menu for provider storage destinations. Selecting this option does not actually enable balancing on the provider destination.

In some circumstances, selecting Print from an action menu in the administration console may fail to print the screen or may print extraneous information.

Selecting Activate from the action menu in the administration console for a deactivated user in an organization that was deactivated and then reactivated does not completely reactivate the user. The user must sign in to the CrashPlan app or SharePlan app on a device to be fully reactivated.