OpenRecords v2.1 - Performance Test

Features that are different for Performance Testing:

• constant AGENCY_USER in user_type_auth will have a value of EDIRSSO.

OpenRecords v2.0.9

Fixes the 500 Internal Server error that is returned when an Agency User tries to generate a CSV from the search page.

Root Cause:
date_created was removed from the results (in the _source) of the elasticsearch query. This led to a key error as result["_source"]["date_created"] is called in the writing of the csv.

OpenRecords v2.0.8

Bugfixes:

• Allows active agency users to upload files.
• Updates date calculation and display for requests submitted directly in portal to accurately reflect timeframes for responses.

Bug Fixes

This release fixes the following bugs:

• Agency descriptions were being shown publicly before a request had been completed.
• The language around acknowledgment due dates and request submission dates has been updated to accurately reflect FOIL.

OpenRecords v2.0.6

Fixes for date calculations and automated notifications for jobs.

Future releases will be created using merged release branches from develop into master.

OpenRecords v2.0.3

Features Deployed

• Activating the Department of Cultural Affairs
• Added fix for incorrect due dates / release dates due to local to UTC conversion
• Fixed issue with public files being inaccessible without a token

OpenRecords v1.2.2

• Fixes issue for agency users submitting requests whose descriptions and summaries are too long.

OpenRecords - v1.2.1

• Bugfix for emails not being sent out to non-portal agencies.
• Fix assignment issue for requests.

OpenRecords - v1.2

• Agency users can now attach documents to emails before they are sent to requesters
• Agency users can now upload files up to 500 MB
• An email response is sent to the requester with a summary of the request

OpenRecords - v1.1.0

• Agency users can now add multiple responsive files at one time
• Email responses to the requester can now be edited by the agency before sending
• Add an agency description for the request
• When a request is acknowledged, a confirming email containing the acknowledgement content is sent to the agency user
• Send full request information by email to all agencies