Nov2015 - LiquidAnalytics/ld-api-examples GitHub Wiki

#Major Changes and New Features Summary

##Cloud: Permanent History Retention Process

This release includes refined process for item schemas that require permanent retention of history:

  • History entries where action=Save are retained for up to 15 days
  • After 120 days, history records are no longer available for SQL querying, but are migrated to long term storage. They can be viewed using mission control.

##Cloud: MC Transactions Blotter Improvements

Transaction blotter can now take advantage of SQL for improved performance and response times.

##Cloud: MC Screen for Sequence Management

MC now has a tool for managing sequence generation.

##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.

##Ability to Exclude a User from loginAs

It is now possible to exclude a user from being an option for loginAs through User Policies. To do so, create or update a policy giving it a PolicyStatement with Application of "Decisions", and Feature of "Login". There will be options for ExcludeFromLogin and ExcludeFromLoginAs which can be enabled. Any users that belong to such a policy will not show up as an option when using the loginAs feature from the device.

##TextSearchTags as Items

TextSearchTags are now stored as items to faciliate synchronization to devices.

Global Callable Functions

It is now possible to create a Global Callable Function which once defined, can be copied for use in any community.

#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 an item with multiple address blocks, all having the same address, would not be properly geocoded.
  2. Fixed issue where using the [EMPTY] filter in an MC item blotter actually resulted in a Null or Empty query being executed, leading to incorrect filter results.
  3. Added headers option for Batch Export.
  4. AuditLog entries will now be created when a users password is changed.
  5. Increased the scope of table corrections possible through the Mission Control Correct Table Discrepancy tool.
  6. Added ability to directly expire a users access tokens through Mission Control. Previously was only possible by actually changing a users password.
  7. No longer create unnecessary indices for history block tables.
  8. All sql table indices created by the system are now done concurrently, to avoid any possible blocking of queries.
  9. Fixed potential integer overflow problem if expireAfterDays on a schema was set to 25 days or greater.
  10. FunctionCallLog for sqlQuery calls will now have information on the item type passed in to the API.
  11. Added ability for Save actions to have transactional workflows if configured.
  12. Items updated as part of a package now have a specific state, "PackageDeployment" so the reason for the item update is obvious.
  13. In Mission Control Item Blotters, when looking at the sync status for a particular user and device, fixed bug where the column "deviceSyncTime" would get added to the blotter multiple times every time you switched to a different device.

#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
11/04/2015 DEV Release available for On-Premise customers
11/04/2015 ProdB
11/05/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** ⚠️