In the existing implementation the data export can only be triggered manually. For the exports that reoccur on regular basis (like incremental export of all records that were added or modified since the last export), the application will need to provide the API so that the export could be triggered by the external custom export script .

This feature covers backend work that would support a scenario when the library has an export job that needs to run on the regular basis on the data identified in a consistent way. Such jobs are mostly run when the exported data is need for integration with the external services and the file generated by the export might need to be FTP-ed to a specific location.

The user should be able to:

1. schedule when the job will need to run (quarterly, monthly, weekly, daily, at a specificied time)

2. determine if this re-occurring export job

3. the files generated by export are stored in the standard location

4. the job will be associated with a mapping profile that will determine required data manipulation.

5. identify the data that will be exported by CQL query that can take system parameters (like date of the last execution) for example or by providing list of UUIDs if static data needs to be exported.

Additional information:
Updated workaround has been attached.