v1.4.5_Production

Aggregate v1.4.5

(January 2015)
🔻 Google disabled functionality used by this installer to upload ODK Aggregate to Google App Engine. See here for the work-around.

1. update to javarosa-2015-01-10 jar.
2. update to jQuery 1.11.1
3. update the ODK 2.0 Data model and Sync protocol (incompatible with device releases: rev 122 and earlier).
4. Fix: support performing mark-as-complete on encrypted submissions (requires ODK Briefcase v1.4.5 or higher).
5. Fix: add server preference to ignore partially inserted/deleted submissions. Logs them but ignores them so that you can access all other rows in your dataset. Disabled by default. By default, all actions fail upon encountering any malformed submission. You should not ignore these failures but should correct them as soon as is practical.
6. Attempted fix: for "Log In" issue -- insert sleep to give Google a chance to propagate clearing of session cookie. Tweak the webpage resize/layout calculations to be more efficient.
7. fix: make incomplete deletions and insertions more recoverable.
8. performance: change MySQL table creation to not declare primary keys and just use ordinary indices for the primary key.
9. security: Support Enketo-express (allow non-https communications with Enketo server). When the communications are not secure, this change discloses the Enketo access token to eavesdroppers.
10. security: Filter out forbidden characters in redirect string to prevent XSS attacks.
11. security: Add clickjacking prevention header as detailed here: https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet

Upgrading

• If you were testing out ODK Tables, you should delete all ODK Tables files and data tables before upgrading, as the database schema has changed. Note that the server no longer works with ODK Sync 2.0 rev 122 (or earlier releases).

v1.4.4_Production

Aggregate v1.4.4

(August 2014)
🔻 Google disabled functionality used by this installer to upload ODK Aggregate to Google App Engine. See here for the work-around.

1. installer now asks for an ODK Aggregate username for the super-user (not a Google e-mail account). Default password is aggregate.
2. banner displayed if super-user's password has not been changed from aggregate.
3. fix: column name generator bug (upload of form definition failed)
4. fix: add more detailed error messages when a submission is corrupted
5. IE6 and IE7 are no longer supported. Upgrade your browser.
6. allow user to specify the ODK 2.0 App Name.
7. allow anonymous access to ODK 2.0 Sync APIs.
8. enforce 'Administer Tables' access for ODK 2.0 Sync APIs that alter server configuration.
9. for ODK 2.0 Sync APIs, remove JBoss Resteasy; use Apache Wink instead.
10. extensive version updates to supporting software libraries.
11. update CONFIGURE.txt instructions for maven builds. Define ANT scripts for external dependencies.

Upgrading

Upgrades require several manual interventions:

• You must have Java 7 installed - the GAE 1.9.7 SDK used within the installer now requires that version of Java. If you are upgrading from ODK Aggregate 1.4.3, you have already done this.
• If you were testing out ODK Tables, you should delete all ODK Tables data tables before upgrading, as the database schema has changed.
• You must flush the session cookies on the server. Session cookies are used to identify the logged-in users of the system. The security software versions were updated in this release, causing the older cookies to become invalid. See below for the upgrade steps.

Assuming you have done (1) and (2) above, the upgrade steps after those are as follows:

1. Open a browser and go to your Google AppEngine dashboard via: dashboard
2. Click through to your application id. Then click on "Memcache Viewer" under the "Data" heading in the left sidebar. Keep this window open.
3. Now, run the installer and deploy ODK Aggregate 1.4.4 to this application id.
4. After it has deployed, click on Flush Cache in the dashboard window's Memcache Viewer screen.
5. Follow the instructions here for changing the password of the super-user username.

Other than the need to flush this cache, and the need to delete any ODK Tables data before upgrading, this should be a seamless upgrade from ODK Aggregate 1.4.x

v1.4.3_Production

Aggregate v1.4.3

(May 2014)
🔻 Google disabled functionality used by this installer to upload ODK Aggregate to Google App Engine. See here for the work-around.

1. updated javarosa jar
2. add stub Tomcat/MySQL Eclipse project with readme
3. update selenium test environment and various 3rd party jars
4. update the GAE SDK inside the installer to 1.9.0
5. new ODK Tables sync protocol and UI. Breaks ODK Tables Alpha 2 sync.
6. new sync protocol exchanges SAVEPOINT_TYPE, FILTER_TYPE, FILTER_VALUE

Upgrading

Upgrades require a manual intervention:

You must have Java 7 installed - the GAE 1.9.0 SDK used within the installer now requires that version of Java.

If you were testing out ODK Tables, you should delete all ODK Tables data tables before upgrading, as the database schema has changed.

Otherwise, this should be a seamless upgrade from ODK Aggregate 1.4.

v1.4.2_Production

Aggregate v1.4.2

(March 2014)
🔻 Google disabled functionality used by this installer to upload ODK Aggregate to Google App Engine. See here for the work-around.

1. Fixes to ODK Tables sync protocol for the combined release.
   Due to interactions with Google AppEngine, the ODK Tables Synchronization protocol does not currently work on Google AppEngine servers. You must install a local server or a VM image in order to use that mechanism

Upgrading

If you were testing out ODK Tables, you should delete all tables before upgrading, as the database schema has changed.

Otherwise, this should be a seamless upgrade from ODK Aggregate 1.4.

v1.4.1_Production

Aggregate v1.4.1

(February 2014)
🔻 Google disabled functionality used by this installer to upload ODK Aggregate to Google App Engine. See here for the work-around.

Summary of changes:

1. Enketo Webforms integration. You can now use Enketo's browser-based Webforms to fill-in and publish submissions directly into ODK Aggregate. This feature was developed and donated by SDRC India. To enable Enketo integration, go to the Site Admin / Preferences tab and click on Enketo API Configuration.
2. fix the Z-ALPHA JSON publisher and the JSON File export to emit an array of zero or more objects, one object per submission, with proper treatment of embedded quotes, etc. Confirmed that the output passes JSLint.
3. fix the CVS File export functionality to double-up all occurrences of double-quotes in a field before surrounding that field with double quotes (per RFC 4180).
4. clean up date and time handling in REDCap publisher and enforce GMT time zone interpretation when rendering date and time strings.
5. various GWT interfaces have been changed to use concrete ArrayList types (reduces code size).
6. new permissions have been added in support of ODK Tables -- Synchronize Tables and Administer Tables and for most ODK Tables interactions, the user is required to have Synchronize Tables permissions.
7. extensive changes to ODK Tables sync protocol and database structures. There will be further changes in the next update.
8. fix sizing calculations and CSS so that the ODK logo does not get clipped or overwritten.

Upgrading

If you were testing out ODK Tables, you should delete all tables before upgrading, as the database schema has changed.

Otherwise, this should be a seamless upgrade from ODK Aggregate 1.4.

v1.4_Production

Aggregate v1.4

(October 2013)
🔻 Google disabled functionality used by this installer to upload ODK Aggregate to Google App Engine. See here for the work-around.

Summary: Major changes to Aggregate's publishers to update to the latest jars and protocols, add new publishers, and improve quota usage.

1. changed behavior: simple JSON publisher now POSTs an application/json entity body; added option for how to treat binary content. Incompatible change; see Upgrading section if you were using the Z-ALPHA JSON Server
2. changed representation: ODK Tabled storage schema has been revised. Incompatible change; see Upgrading section if you used your server to upload or download data to ODK Tables. Syncing with ODK Tables is broken in this release. Only v1.3.4 on Google AppEngine works with the ODK Tables alpha (we are in the middle of changing table schemas).
3. fix: file exports were not properly writing UTF-8 character sets.
4. fix: postgreSQL failures on some forms (column names must be less than 63 characters)
5. Upgrade Aggregate’s Google publishers to use the updated Oauth2 libraries (e.g., Google Fusion Tables, Google Spreadsheet). Publishing from Google Apps domains does not work (it never has). This required a significant rewrite of the publishers so please notify the ODK core team of bugs!
6. NEW: Add support for publishing data to Google Maps Engine, more information can be found at GoogleMapsEngineInstructions
7. rework Spreadsheet and Fusion Table publishers to use Google libraries (consistent with the new Google Maps Engine publisher)
8. additional active-paused state in publisher to extend the delay in publishing attempts (and reduce quota usage) if the destination publisher is reporting an error.
9. improved how failures during form definition uploads are rolled back to increase the likelihood that the database is restored to a clean state.

Upgrading

You may need to clear your browser cache to complete the upgrade. If the browser screen flickers after upgrading, first clear your browser cache and reload the page.

If you were using the Z-ALPHA JSON Server, you must delete all instances of that publisher before upgrading. After upgrading, the updated publisher will send a single application/json entity body to the external server instead of a multi-part form containing that entity.

If you were using ODK Tables with ODK Aggregate, you need to delete all the ODK Tables data on ODK Aggregate before upgrading.

v1.0.9_Production

Aggregate v1.0.9 Production

1. fix issue 598 (on Google Code) - AppEngine over-quota page showing erroneously.

Upgrading

See v1.0.4 Production Upgrading instructions.

v1.0.8_Production

Aggregate v1.0.8 Production

1. fix erroneous release of TaskLock that could cause 60-second lock-out of "Add Forms", causing slow uploads of multimedia forms using FormUploader or Briefcase
2. fix performance bugs in the TaskLock for GAE.
3. fix correctness bugs in the TaskLock for MySQL and PostgreSQL that can cause two TaskLocks to be obtained for the same resource if they are both requested at exactly the same second.

Upgrading

See v1.0.4 Production Upgrading instructions.

v1.0.7_Production

Aggregate v1.0.7 Production

1. fix issue 505 (on Google Code) - double "Add Forms" leaves UI in inoperable state
2. fix issue 506 (on Google Code) - double "Add Forms" leaves UI in inoperable state
3. JSON file export supported
4. update installer to use Google AppEngine 1.6.4 SDK
5. remove uiVersion comparison tests (deprecated functionality).

Upgrading

See v1.0.4 Production Upgrading instructions.

v1.0.6_Production

Aggregate v1.0.6 Production

1. fix issue 542 (on Google Code) - Add a Refresh Credentials button on publishers. This button appears when the publishing to an external service (Google Spreadsheet or Fusion Tables) fails with a 401 (Unauthorized) error. Clicking the button will walk through the authorization screens for publishing to that service, yielding a new credential for that publisher.
2. fix issue 512 (on Google Code) - Add a Purge Submission Data button on the Form Management / Submission Admin tab. This button enables you to delete submission data up to a specified date. Incomplete submissions are not deleted.
3. fix issue 422 (on Google Code) - digest auth failing in 1.0.5 Release Candidate.
4. Includes all functionality from the 1.0.5 release candidate.

Upgrading

See v1.0.4 Production Upgrading instructions.