Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
XL < 15 days
-
Medium
-
Large < 10 days
-
Concorde
-
-
115
-
This feature will allow user to see the details of the data export job and is crucial for troubleshooting
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
-
R1
Description
There are three elements of this functionality:
1. Landing page - Logs container
This functionality has been mostly implemented but will need to support a scenario when the export generates multiple files, with each file name being a link to the generated file. When user clicks each file name the files are downloaded.
2. View All option
This will display a new form that will contain list of all jobs. How long the logs are being preserved will be determined by tenant level settings. The jobs will be searchable by ID, generated file name, date of execution, job profile and name of the user who triggered the job.
3. Detailed log
This will be accessible by clicking the whole row of listed jobs on the landing page (for recently completed jobs) and View All form. The log will contain a list of all records that were exported (successful and failed) in their designated format. User should be able to filter by successful/failed records. Failure should be displayed in with details (missing or invalid data, for example). The initial implementation could be similar (if not identical) with data import detail log (see attached screenshot)
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-652
Metadata Record Export
-
- In progress
-
- is defined by
-
MDEXP-107
Query completed export jobs by job's HRID
-
- Closed
-
-
MDEXP-108
Query completed export jobs by file name generated by the job
-
- Closed
-
-
MDEXP-111
Query completed export jobs by job profile
-
- Closed
-
-
MDEXP-112
Query completed export jobs by user who run the job
-
- Closed
-
-
MDEXP-113
Query completed export jobs date range
-
- Closed
-
-
MDEXP-259
Log errors for Holdings records export
-
- Closed
-
-
MDEXP-261
Create API GET/data-export/logs/{jobExecutionID} for error log handling
-
- Closed
-
-
MDEXP-262
Create a link to the inventory record if the export fails
-
- Closed
-
-
STDTC-6
Spike: Explore view all logs page from data-import
-
- Closed
-
-
UIDEXP-18
Data Export App - landing page - view detailed log of failed job
-
- Closed
-
-
UIDEXP-62
Data Export App - landing page - add "View All" button
-
- Closed
-
-
UIDEXP-63
Data Export App - landing page - open "View All" page
-
- Closed
-
-
UIDEXP-97
Add Error column to the list of completed jobs on the landing page
-
- Closed
-
-
UIDEXP-142
View logs - main pane
-
- Closed
-
-
UIDEXP-144
Render error log details
-
- Closed
-
-
UIDEXP-145
Change query for rendering jobExecutions
-
- Closed
-
- relates to
-
MDEXP-256
Modify status of the completed export job
-
- Closed
-
-
MDEXP-257
Log errors for inventory Instance record exports
-
- Closed
-
-
MDEXP-258
Introduce error codes for errors during data export
-
- Closed
-
-
MDEXP-260
Log errors for Inventory Item records export
-
- Closed
-