Dec2015 - LiquidAnalytics/ld-api-examples GitHub Wiki

#Major Changes and New Features Summary

##Cloud: Socket-Based Sync (experimental feature only)

Devices can now sync using a high-speed socket connection and will received changes as soon as they are available without the need to poll the server every 3 minutes. The 3 minute polling sync remains in place for connectivity scenarios where the socket may not be fully established (such as some hotel wifi networks)

This is an experimental feature that is only enabled in DEV and QA at the moment.

This release includes further refinements to the socket-based sync protocol. Estimated release to production is January 2016.

##Cloud: GitHub Integration

MC users can connect their accounts to github and associate their community with a github repository. Changes to config items require comments which are recorded into github as commits.

Can view history of git commits for a configuration item in Item History Explorer.

##Cloud: Preliminary Swagger support

We are beginning to roll out support for Swagger. Apps can be built using standard Swagger files.

##Limits and trends

This release includes a number of fixes to improve calculation of limits. Added limits graph to the dashboard tab in Mission Control for viewing limit data over the previous 60 days.

##Cloud: Support for AWS RDS read-replicas (expermiental feature only)

We now support read replicas, allow us to elastically scale out a community's data store during times of high volume -- such as OND for our wine and spirits communities.

##Cloud: Logical Separation of RDS Connection Pools

Prevent the situation where during period of high volume it becomes difficult to log on using Mission Control and perform administrative tasks.

##Cloud: Fail-fast RDS Connection Pools

Prevent lock-ups that could be caused by long-running SQL queries.

##Cloud: Multiple Communities Belonging to Same Customer Can Reside in the Same RDS

Some customers utilize multiple communities. In order to support cross-community SQL queries the data stores must reside on the same AWS RDS instance.

##Cloud: Community Override Header

An app used by the user that belongs to multiple communities may now explicitly specify which community the operation is being performed against.

##Switch User

Users with "Login As" enabled can now switch their active user from within the app without full registration.

#Change Log

  1. Block transaction tables do not require indices, save disk space.
  2. The system no longer indexes or inserts values into h_id,h_clientId or h_revisionId in any block tables - these values were never used.
  3. "Save" transactions are no longer recorded in the _txn sql tables.
  4. Fixed a bug in MC PolicyManagementPanel where if the panel refreshes while a user is being added, the user might be added to the wrong policy.
  5. Fixed issue where we would incorrectly put the string "null" into DeviceInfo table rather than just the null value.
  6. Queries done from MC Transaction blotter now properly make use of max rows limit and sort by.
  7. Truncate command for Cloud environment now does truncate of sql table, rather than drop / recreate of table.
  8. Fixed a bug where if an item type was configured for entitlement through Entitlement Queries only, and not a relationship path, they would not be considered an item for sync, and would never sync to a users device.
  9. Fixed an issue with Bulk Update command, where clearing out the value for a field would not work in certain cases.
  10. Fixed an issue with sending deletes via Upsert api, where the data of the item to be deleted would be taken from the api call, which might not necessarily match the most recent version of the item being deleted, which could lead to realtime repermissiong issues.
  11. Fixed an issue where deleted verified items would never be removed from a given devices Device Sync Status view in MC, which would incorrectly make it look like deletes are never verified.
  12. Fixed some bugs with our queue polling strategy which sometimes left a processing queue starved for long period of times.

#Risks and Known Issues

There are no known issues or risks.

#Maintenance Window

This server deployment does not require a maintenance window.

#Special Deployment Notes

There are no special notes for this release.

#Release Schedule

Date Environment
12/2/2015 ProdB
12/3/2015 Prod

#ProdB Validation

Testers assigned to each customer use the current production client app to verify there are no new issues introduced in ProdB:

  1. In settings change the server URL to https://ldcloud-b.liquidanalytics.com
  2. Perform exploratory testing
  3. Report only new issues found, distinguishing between what may be caused by the server from what is a client-side issue
    • Sync
    • Transactions
    • Registrations
    • Authentication
    • On-demand functions
    • Queries

#Prod Validation

Testers assigned to each customer use the current production client app to verify there are no new issues introduced in Prod:

  1. In settings make sure the server URL is https://ldcloud.liquidanalytics.com
  2. Perform exploratory testing
  3. Report only new issues found, distinguishing between what may be caused by the server from what is a client-side issue
    • Sync
    • Transactions
    • Registrations
    • Authentication
    • On-demand functions
    • Queries
⚠️ **GitHub.com Fallback** ⚠️