Details
-
New Feature
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
None
-
-
XL < 15 days
-
Medium
-
XL < 15 days
-
Concorde
-
-
110
-
This feature will combine all elements of data export - and it will be a place where user will be starting manual exports and scheduling reoccurring
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
Description
In Export Manager, the user will start a new job by selecting the .csv file with unique identifiers of the records to be exported. The files can be browsed on the user's local system or be dragged and dropped to start a new job.
On the landing page the user will be able to see see the list of the running jobs and the logs of recently completed jobs.
The records that will be a part of the export will be determined by selecting previously defined query (UXPROD-978) or by providing a file with a list of record identifiers that can be also be saved from the Inventory search.
The list of all jobs currently in progress,will provide details like export job id, used job profile, who ran the job, etc,
The log in addition to information listed in current job listing, will specify if the export was successful. For the successful runs it will contain the link to the file so the user can download the file to the local machine. This will be possible only for the smaller export files.
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-652 Metadata Record Export
-
- In progress
-
- is defined by
-
MDEXP-42 File upload functionality
-
- Closed
-
-
MDEXP-43 FileUploadService: create DAO for FileDefinition
-
- Closed
-
-
MDEXP-44 FileUploadService: implement ability to save file data
-
- Closed
-
-
MDEXP-45 FileUploadService: Create REST API to upload file
-
- Closed
-
-
MDEXP-47 File export, storage and retrieval
-
- Closed
-
-
MDEXP-49 StorageCleanupService: ability to clear up file storage
-
- Closed
-
-
MDEXP-53 Create documentation for the file uploading
-
- Closed
-
-
MDEXP-56 File Export Storage Implementation
-
- Closed
-
-
MDEXP-58 Create InputDataManager
-
- Closed
-
-
MDEXP-60 POC: Saving files to S3
-
- Closed
-
-
MDEXP-68 Create a S3 bucket for a tenant
-
- Closed
-
-
MDEXP-69 Update a jobExecution entry in DB
-
- Closed
-
-
MDEXP-70 Add fileName field to Job
-
- Closed
-
-
MDEXP-74 Add file extenstion valiation to /data-export/fileDefinitions and /data-export/fileDefinitions/{id}/upload
-
- Closed
-
-
MDEXP-79 Provide Human Readable JobId
-
- Closed
-
-
MDEXP-80 Provide Number of Records
-
- Closed
-
-
MDEXP-81 Provide First name and Last name of the user who triggered the export job
-
- Closed
-
-
UIDEXP-5 Data Export App - landing page - selecting file with UUIDs
-
- Closed
-
-
UIDEXP-6 Data Export App - landing page - view running jobs
-
- Closed
-
-
UIDEXP-7 Data Export App - landing page - view logs of completed jobs
-
- Closed
-
-
UIDEXP-11 Data Export App - landing page - file selection area
-
- Closed
-
-
UIDEXP-19 Data Export App - landing page - accessing the file generated by export
-
- Closed
-
-
UIDEXP-21 Validating file with UUIDs and display an error message if invalid
-
- Closed
-
-
UIDEXP-23 Periodically update the list of logs and running jobs in order to see the updated data (with integration with the backend)
-
- Closed
-
-
UIDEXP-35 Data Export App - landing page - populate JobId
-
- Closed
-
-
UIDEXP-36 Data Export App - landing page - populate Records column
-
- Closed
-
-
UIDEXP-37 Data Export App - landing page - populate Run by column
-
- Closed
-
- relates to
-
UXPROD-2328 Export landing page - canceling long running jobs
-
- Draft
-
-
UXPROD-2329 Export Manager - queued jobs
-
- Closed
-
-
UXPROD-2330 Scheduling export of inventory records through an API
-
- Open
-
-
UXPROD-2331 Export Manager - accessing export files - hosting agnostic
-
- Closed
-
-
UXPROD-2333 Export Manager - triggering export of Inventory instances by providing file with CQL query
-
- Closed
-
-
UXPROD-4309 Export landing page - pausing and resuming running jobs
-
- Draft
-