BlackBerry Web Services fixed issues

In previous releases, if you used BWS.createUserEmailProfiles to create an email profile, you could not override the default settings that were obtained from Microsoft Active Directory. (DT 6771852)

In the BlackBerry Web Services 6.2 MR1, the useADSettings field has been added to the NewUserEmailProfile and UserEmailProfile classes. If this field is set to true, user data for the email profile is obtained from Microsoft Active Directory. Otherwise, the data specified in the following fields is used for the email profile: accountName, domain, emailAddress, and username.

The overview page of the BlackBerry Web Services API Reference has been updated to include the date format, explanations of key concepts, the RequestMetadata definition, and a list of error codes that are common to all available APIs. Links to the common error codes have been added throughout the API reference where applicable. (DT 6534455, DT 6457702)

In the BlackBerry Web Services API Reference, the method detail section on the interface BWS page was not organized alphabetically. (DT 6424897)

In the BlackBerry Web Services 6.2, this issue is resolved.

The BlackBerry Web Services did not validate the organizationUid field in the RequestMetadata class. (DT 6375194)

In the BlackBerry Web Services 6.2, this issue is resolved.

The BlackBerry Web Services did not validate the locale field in the RequestMetadata class. (DT 6375069)

In the BlackBerry Web Services 6.2, this issue is resolved.

Performance improvements have been made to the BWS.getBESHAPools method. (DT 6312656)

Performance improvements have been made to the BWS.getServersDetail method. (DT 6311482)

The BWS.getUserActivations method does not validate parameters that are not supported by the BlackBerry Device Service. The interface BWS page in the BlackBerry Web Services API Reference describes which parameters are not supported by the BlackBerry Device Service. (DT 6046648)

If the searchCriteria parameter in BWS.getUsers contained an invalid UID, an UNKNOWN error message was returned. (DT 6005175)

In the BlackBerry Web Services 6.2, if searchCriteria contains an invalid UID, an INVALID_PARAMETER error message is returned.

If an application used the BWS.createUsers method to create a user account, and the user account already existed on the BlackBerry Device Service, a misleading error message was returned: "Failed to create user: Mail account not found." (DT 5969419)

In the BlackBerry Web Services 6.2, a more descriptive error message is returned.

In the BWS.getUsersDetail method, loadITPolicies returned a failure for users that were not BlackBerry device-enabled. (DT 5934408)

In the BlackBerry Web Services 6.2, the BWS.getUsersDetail method verifies that a user is BlackBerry device-enabled before requesting data for IT policies, software configurations, VPN configurations, WLAN configurations, and email profiles.

For all search methods (for example, BWS.getUsers), if the value of a parameter is “” or null, the parameter is considered unspecified and the search on this field is not attempted. (DT 5843567)

The BWS.getSWConfigApplications method might have returned a Runtime exception due to an error in the sortBy parameter. (DT 5833002)

In the BlackBerry Web Services 6.2, this issue is resolved.

In the BlackBerry Web Services API Reference, the interface BWS and interface BWSUtil pages did not describe whether the impact of each API was immediate or queued. (DT 743527)

In the BlackBerry Web Services 6.2, this issue is resolved.

In previous versions of the BlackBerry Web Services API Reference, the itPolicy parameter in the BWS.setGroupsITPolicy method and the BWS.setUsersITPolicy method was listed incorrectly as itPolicyObject. This error is corrected in the API Reference for the BlackBerry Web Services 6.2.

In previous versions of the BlackBerry Web Services API Reference, the individualRequests parameter in the BWS.setUsersResendReconciledApplications method was listed incorrectly as setUsersResendReconciledApplicationsIndividualRequest. This error is corrected in the API Reference for the BlackBerry Web Services 6.2.



Was this information helpful? Send us your comments.