Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2330

Inventory instance export - scheduling jobs through APIs

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Potential Workaround:
      Hide
      *Start the export:*
      1. Post file definition to /data-export/fileDefinition (this is an equivalent of uploading UUIDs or CQL)
      2. Start the export by /data-export/export
      *Retrieve the files generated by the export:*
      1. Get completed jobExecutionId and fileId : /data-export/jobExecution - by querying by completed time stamp
      2. Download the file by /data-export/jobExecutions/{jobExecutionId}/download/{fileId}
      Show
      *Start the export:* 1. Post file definition to /data-export/fileDefinition (this is an equivalent of uploading UUIDs or CQL) 2. Start the export by /data-export/export *Retrieve the files generated by the export:* 1. Get completed jobExecutionId and fileId : /data-export/jobExecution - by querying by completed time stamp 2. Download the file by /data-export/jobExecutions/{jobExecutionId}/download/{fileId}
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Development Team:
      Firebird
    • Calculated Total Rank:
      89
    • PO Rank:
      90
    • PO Ranking Note:
      Needed for automated exports
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Grand Valley (Full Sum 2021):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R3

      Description

      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 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, specific time)
      2. determine if this re-occurring export job
      3. determine what should happen with the files that are generated through the export (FTP or accessible through the link)
      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.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                magdaz Magda Zacharska
                Reporter:
                magdaz Magda Zacharska
                Back End Estimator:
                Magda Zacharska Magda Zacharska
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases