• Fixed cross-site scripting vulnerability
• Improved the automated web tests
• Updated development dependencies

• Added new options for transformation rules auto-generation, including the following options:
  • re-generate rules before each run
  • combine all non-repeating forms into the same table for non-longitudinal studies
  • include survey fields
  • remove notes fields
  • remove identifier fields

• Upgraded REDCap-ETL dependency to version 1.5.4: https://github.com/IUREDCap/redcap-etl/releases/tag/1.5.4

• Added ETL server permissions; server permissions can now be set to:
  • Public - anyone can access (this was the only option available previously)
  • Private - admins, and anyone explicitly specified by admins can access
  • Admin - only admins can access
• Upgraded the REDCap-ETL dependency to the 1.5.3 version, which has bug fixes

• Added pre-processing SQL (specification of SQL that is run before the ETL process)
• Added generation of primary and foreign keys in database tables
• Fixed bug that occurred when a REDCap project that had ETL configurations was copied

Upgraded the REDCap-ETL dependency to 1.4.5: https://github.com/IUREDCap/redcap-etl/releases/tag/1.4.5

• Upgraded the REDCap-ETL dependency to 1.4.4: https://github.com/IUREDCap/redcap-etl/releases/tag/1.4.4

• Added options for adding DAG (Data Access Group) and file fields for auto-generation of transformation rules
• Added help for transformation rules auto-generation
• Changed API URLs in ETL configurations to be calculated dynamically, so that if you migrate or clone a REDCap instance with the REDCap-ETL Module, the module will automatically reference the new REDCap instance

• Added support for PostgreSQL as a database where extracted REDCap data can be loaded

• Added support for SQL Server as a database where extracted REDCap data can be loaded
• Added logging for admins
• Added option to generate form complete fields for auto-generation of transformation rules
• Removed ability to show database passwords in ETL configurations (for security reasons)