Jan2016 - LiquidAnalytics/ld-api-examples GitHub Wiki

#Major Changes and New Features Summary

##Cloud: Performance Metrics The Dashboard Panel in Mission Control has been overhauled and expanded. Existing graphs that displayed daily and total data loads and daily transactions have been upgraded with date and item type filters to increase usability. Additional graphs featuring entitlement counts, entitlement query performance, scheduled permissions run time, and many other system metrics have been added.

##Cloud: SQL On Demand Functions It is now possible to configure on demand sql queries through HttpRestFunctionConfig, which have the inherent benefit of caching behavior that all Passthrough functions have.

##Cloud: JWTTokens (experimental feature only) We have altered our tokens to match the JSON Web Token RFC7519 industry standard. This allows our tokens themselves to carry information on the subject who has been granted the token, and allows the possibility of securely verifying a token using a public key, without needing to communicate with the Liquid Server directly.

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

##Cloud: In-memory sync cache

We now utilize AWS ElastiCache for sync to dramatically increase sync performance and ability to handle thousands of concurrent devices syncing.

#Change Log

  1. In Mission Control Schema Management, added ability to detect if a view schema does not properly list out all of its dependent view types. Such schemas are displayed in magenta until they are fixed.
  2. When an item is transacted, source and sourceId header fields are now stamped with values 'Transaction' and the transactionId respectively. This allows us to easily link all the history records for a single transaction to each other (ReceivedFromDevice, SendingToApplication, TransactionCompleted), especially through queries.
  3. In Mission Control Item Blotters, the User Id filter box that is used to search for items that are entitled to the given user no longer requires case of the userId to be exact in order to return proper results.
  4. Fixed issue in internal query mechanisms that enabled a large query sent from SqlQuery API to potentially cause memory issues on the server.
  5. Fixed concurrency issues where multiple servers could potentially dead lock each others sql queries when initializing a new table or index.
  6. Added tasks that can track overall progress of a SetupUserPermissions run on multiple user, including the overnight run. History of these runs can be viewed under MaintenanceTaskStatus blotter, where TaskType is ScheduledPermissionRun.
  7. In Mission Control Item Blotters or Schema Management Panel, it is now possible to filter schemas by bundle, as well as by View or Materialized Views.
  8. QueryName has been added as a post parameter to the /data/sqlQuery API to be used in gathering metrics. (See SQLQuery Api for more details)
  9. In Mission Control Callable Functions panel, while editing a function inline, after hitting the Save button, we no longer automatically end the inline editing, users may continue to editing without having to reopen the function.
  10. Fixed issue with the way filters on Int and Decimal datatypes work. Prior to fix, a filter such as decimalField = 5 would fail to match to items where the value was 5.0, and vice versa for intFields.
  11. Now possible to filter on Int and Decimal datatypes using >, >=, <, <= symbols through any interfaces that take in a map as a filter. For example {"intField": ">10"} can be sent to denote filtering where the vlue of intField is greater than 10.
  12. FuncionCallLog items are now eligible to be processed by Callable Function Triggers.
  13. Fixed issue where multiple filters specified on a Trigger item or a WebhookTrigger item would not properly limit which items are sent to the trigger. The multiple filters were acting as an 'OR' when they should have been acting as an 'AND'
  14. Added state AdminProcess which can be used to inline update and entitle an item by the updater, without having to wait for full entitlement logic to run.
  15. In MissionControl Item Explorer, if we detect that the item contains data that includes escaped strings, an additional tab will be enabled to allow for easier viewing and copy/pasting of the escaped strings.
  16. Callers to the /data/query/ api can now specify the query parameter "admin" to true, in order to avoid restricting query results to user entitlement.
  17. Added logic for role 'LoginAsSalesRep', which is similar to 'LoginAs' but restricts the list of users to only Sales Reps.

#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
1/6/2016 ProdB
1/7/2016 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** ⚠️