Releases: lsgs/redcap-copy-data-on-save
Releases · lsgs/redcap-copy-data-on-save
1.4.4 Bug fix for system settings dialog
1.4.3 Bug fixes for copying repeating data, deprecate DAG mapping
Bug fix with copying within record from repeating instrument to other event.
Bug fix read of dag from repeating trigger event/form.
Deprecation notice on DAG mapping option (use @CALCTEXT field copy to redcap_data_access_group instead).
1.4.2 EMF v15, bug fix
- Fix for capture of autonumbered destination record id into longitudinal source project field
- Update to EM framework v15
1.4.1 EM Framework v14
Bump config to v14 of EM framework
1.4.0 Summary page
New features added:
- Summary page
- Fail alert email addresses
- (Superuser only) Include save data in logging
1.3.1 Config setting for name/description
Config setting for name/description, including update to readme.
Fix link to repo in readme
1.3.0 Additional record match/create options, delay option
- Expanded record matching/creation options:
- Match record id (do not create) - backward compatible with previous (do not create record if no match found option)
- Match record id (create matching) - backward compatible with previous (create record if no match found option)
- Match record id (create auto-numbered)
- Look up via secondary unique field
- Option to delay CDoS instructions until after other modules have executed their redcap_save_record() hooks (e.g. Realtime Randomization, REDCap REST).
1.2.0 File upload fields
New features and bug fixes
- Support for file fields in copy instructions
- Disable rules pointing to other projects when enabling module (for safety in copied projects, for example)
- Improved logging
- Bug fix of DAG copy to arm nums > 1
1.1.1 Minor improvements
Minor improvements:
- Copy to new or specified instances using
redcap_repeat_instrumentandredcap_repeat_instancein destination fields config - Improved error checking and handling
- EM framework update
1.1.0 Supports repeating field as record for destination
You can now use a field that is repeating in the source project as the record id used for the destination project. For example:
- Source project is a household-level project and contains repeating instrument for household members
- Repeating instrument contains a field with
@CALCTEXT(concat([record-name],'-',[current-instance])) - Destination is a member-level project