Oct2015 - LiquidAnalytics/ld-api-examples GitHub Wiki

#Major Changes and New Features Summary

##Enforcement of Items-Loaded Limits

This release includes enforcement of the Items-loaded limit as described below. Default configuration is:

  • Total item updates per licensed user: 1500
  • Item updates per type per licensed user: 750

When the number of item updates reaches a total of 1500 per user or 750 per item type (whichever comes first) the system will accept and store the items. However, the processing behavior will be as follows:

  • Items will get delivered to all currently entitled users and devices as normal.
  • Items will be sent to all new users, and removed from existing users who are no longer permissioned during the next nightly permissioning process.

If the per-type limit is hit then the above processing rules take effect for that type only. If the total item limit is hit then the above processing rules take effect for all types.

The limit is reset daily. Default setting is 8pm EST, however it can be adjusted in the community config. The recommended setting is to match this configuration to the same time as the nightly permissioning process.

Limits can be monitored in MC CommunityLimitStatus blotter.

##Monitoring of Maintenance Tasks

Maintenance tasks may now be monitored using MC MaintenanceTaskStatus blotter in a format that is easier to query and process than SystemNotification.

##Email REST API

A rest API has been exposed on Liquid Server that allows the sending of emails. For full details see: Email API.

##User Status Item

A common schema called system.UserStatus has been added. Items of this type keeps track of user invitations to a community, and the first and most recent time a User has logged into a community.

##Cloud: SQLQuery API working properly for history queries

The SQL Query API has been updated to properly handle item queries based on history tables. Prior to this change, querying on a history table with item type specified would not return the proper number of history results or properly faulted in blocks on the history results. Add a boolean form parameter "history" to your sqlQuery API request to specify whether the query is to a history table or not. For full details see: SQL Query API.

In addition, on the Mission Control SQL Scratch Pad, there is a checkbox for controlling the history form parameter, allowing users to make use of this added API functionality.

##Cloud: Socket-Based Sync

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)

##Cloud: Temporary SQL History Expiration

Item types that do not have permanent history retention enabled undergo the process. History records older than historyRetentionDays setting on the schema (default is 30 if not set) are deleted with the exception of:

  • Current version
  • Previous version
  • Most recent deleted version
  • Most recent transaction flow
  • Package versions

The details on the history retention rules will be provided separately.

##Cloud: Office365 Outlook Integration

The system now supports integration with Office365 Outlook for appointments.

##Cloud: Materialized View System Notification Improvements

SystemNotification for materialized view refresh is split up for easier monitoring and diagnostics.

##Cloud: Time-based Callable Functions

The functionality of Callable Functions has been expanded to support scheduled execution of a Callable Function based on a static schedule, and based on the date fields of a given item type, in addition to the existing Trigger based Callable Functiosn. For full documentation on Time based callable functions, see: Callable Functions.

#Change Log

As compared to the build currently in production, the following is a list of changes not mentioned in Major Changes section:

  1. Fixed issue where root community would not have access to common schemas in some cases
  2. In Mission Control SQL Scratch Pad, if an sql query times out due to read time out, or gateway time out, user is now notified, rather than it looking like the query returned 0 results
  3. Fixed deadlock scenario that occurred rarely, related to getting dataWarehouseReplicator for a community
  4. Fixed issue in Mission Control Policy Management, when trying to add new users to a Policy, it could take minutes before the user list would show up.
  5. History record is now recorded before any item is sent to a Callable Function for execution through a Trigger or ScheduledTrigger.
  6. In Mission Control - Correct Schema Table Discrepancies action, additional discrepancies such as the existence of extra columns or absence of needed columns, is now detected and alter statements can be run to correct.
  7. Improved detection and reporting of circular entitlement paths
  8. Fixed filter issue in Mission Control, where if on a text field, you set the filter to be != ('not equal to'), and then switched the filter field to a date field, the not equals would apply to the date filter and cause incorrect results

#Risks and Known Issues

No known risks or issues.

#Maintenance Window

This server deployment does not require a maintenance window.

#Special Deployment Notes

It is recommended that each community is configured so that the Limit Reset Hour is set to match the Nightly Repermissioning Hour. The default value is 8pm.

#Release Schedule

Date Environment
9/30/2015 QA Release available for On-Premise customers
9/30/2015 ProdB
10/1/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** ⚠️