VMWare order: an incorrect error message is displayed if a name is too long
Adds the sourcePort property to the SoftLayer_Virtual_Guest_BrowserConsoleAccessLog class
Fixing compliance reports tool.
Updated the way we determine if a billing item has a reclaim transaction for Storage As A Service billing items. Allow customers to reclaim a storage as a service billing item that has been previously un-cancelled.
Fix UI so that an impatient user cannot make multiple requests by banging on the button.
Improve the message in getApiAuthenticationKeys method when subuser get the key of another
Deprecating SoftLayer_Network_Subnet_IpAddress_Global::route and SoftLayer_Network_Subnet_IpAddress_Global::unroute, which will continue to function as proxies to SoftLayer_Network_Subnet::route and SoftLayer_Network_Subnet::unroute, respectively. A transaction record will no longer be returned from either endpoint.
Add payment type validation for anonymous orders in the API.
exposed API call that allows the customer to check on the most recent timestamp of the replication process.
Don’t allow duplicate volume to be refreshed while duplicate provision is still happening.
Automatically cancels billing of dependent duplicates if any existing for a primary volume
VSI with more than 128 GiB memory should not boot into rescue mode.
ApiKeys should now only be visible to the owner of the api key. The master user will be able to see if a user has a key, but not the actual value of the key.
Return false instead of exception for SoftLayer_Network_Storage::isIndedicatedServiceResource function.
Improved SLDN documentation on SoftLayer_User_Permission_Group_Type
Added new api for disaster recovery failover for Network Storage volumes.
Added a check in failbackfromReplicant to prevent flagged parent volume from failing back
Added Method to get a firewalls version: SoftLayer_Network_Vlan_Firewall::getFirewallFirmwareVersion
SoftLayer_Network_Message_Delivery::sendEmail() endpoint has been deprecated and will be removed in API version 3.2
For current Network Storage replicas, a race condition exists where the replication will occasionally start before the snapshot is taken. This causes the latest snapshot to occasionally not be copied to the replica. To solve this race condition, replication will now start 5 minutes after the scheduled snapshot. The 5 minute delay will only affect new replica provisions. Current provisions will continue to replicate at the same time as the scheduled snapshot. To upgrade a current replica to the new 5 minute delayed replication schedule, the current replica must be canceled and re-ordered.
Provided ability to provision file and block storage in a dedicated cluster.