Major Changes and New Features Summary

(Cloud Only) OpenAPI CRUD interfaces are now finalized

OpenAPI interfaces for sending data into LPS are now supported across all environments. The OpenAPI interface should be used for all future integration projects. OpenAPI documentation is segregated by schema bundle within each community.

(Cloud Only) All SQS Queue usage has been highly optimized

LPS heavily utilizes Amazon SQS and the usage of SQS has been made much more efficient. Messages are now processed faster, with less queue polling, and using a smaller number of queues. Failed messages are now retried. Performance and utilization is now tracked in a more consumable way.

(Cloud Only) GET variant of /tokenInfo API

A lighter-weight version of the /tokenInfo API has been added (invoke using GET vs POST method). This call will return much faster but with less information.

Change Log (all changes are cloud only unless otherwise noted)

1. (Cloud and On-Prem) A bug has been resolved that would cause out of order item versions to be replicated. (This bug would sometimes allow sales reps to resubmit the same order multiple times)
2. MC 'Invite User' function now accepts a comma separated list of email addresses. This list can contain complex entries such as '"Alvarez, Jose" [email protected]'
3. A bug has been resolved that would sometimes prevent all scheduled tasks from running within a community.
4. A bug has been resolved that would sometimes cause SQL related errors to be logged upon server startup.
5. A bug has been resolved that would sometimes cause multiple versions of SystemNotifications to be generated.
6. User deletion APIs now clean up any UserRole and UserPolicy items associated with that user.
7. Cross region replication SQS queues are now only enabled for environments and communities with CRR configured.
8. Asynchronous errors with item processing are now tracked within SystemNotifications rather than being silently ignored.
9. Save Layout in MC now saves the selection of the "schema bundle chooser"
10. A bug has been resolved that would cause transaction records to be enqueued for replication even if no replication slave was listening for them.
11. Media thumbnails are now deleted when the media is deleted.
12. Fixed a bug that would cause MC to crash if an invalid community config was imported.
13. REST calls made with null or empty tokens are now rejected more quickly and efficiently.
14. Per-server tracking of all remaining calls into Cassandra has been added.
15. A bug has been resolved that would sometimes cause SystemUser records to be de-indexed.
16. A bug has been resolved that would cause MC searches to run twice - Once vs the SQL index, and once vs the Cassandra index.
17. Callable functions now specify runtime of "nodejs4.3" instead of "nodejs"

Risks and Known Issues

No known risks or issues.

Maintenance Window

This server deployment does not require a maintenance window.

Special Deployment Notes

1. One node of the prior version of the server (Jan 2017) should be removed from the load balancer and left running to drain all deprecated queues. Once all deprecated queues are drained, this node can be removed.

Release Schedule

Date	Environment
2/1/2017	ProdB
2/2/2017	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