Uploaded image for project: 'mod-gobi'
  1. mod-gobi
  2. MODGOBI-157

Define and implement API for retrieving GOBI mapping configs

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • 2.5.0
    • None
    • ACQ Sprint 144, ACQ Sprint 145, ACQ Sprint 146
    • 3
    • Thunderjet
    • Nolana (R3 2022)
    • TBD

    Description

      Purpose/Overview:
      As a system administrator,
      I want to be able to access the details I need to setup the GOBI integration
      so that I don't need to contact FOLIO support to setup or adjust my GOBI integration

      Requirements/Scope:

      1. Return list of order types for which integration is possible
      2. Return GOBI integration default or custom mappings based on order type

      Approach:
      1.1 Add new schema OrderMappingsCollection.json which is collection of mod-gobi\src\main\resources\OrderMappings.json
      1.2 Define API GOBI integration default or custom mappings based on order type → APIs GOBI mapping
      1.3 Implement API GOBI integration default or custom mappings based on order type -> Implement API for retrieving GOBI mapping configs

      Acceptance criteria:

      • API defined and implemented
      • Unit tests created
      • API test created

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-3681 GOBI integration user interface

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done before

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIGS-5 Allow user to edit mappings

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIGS-6 Allow user to reset to default configuration

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is blocked by

            Bug - A problem which impairs or prevents the functions of the product. RMB-933 Fail to generate POJO by schema with self reference elements

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is cloned by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEXPW-225 Improve performance of retrieving orders for EDIFACT export

            • TBD - To be determined
            • Closed
            is duplicated by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODGOBI-159 Define API and update schemas for retrieving Folio fields and translators

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            mentioned in

            Page Loading...

            Activity

              People

                Nosko Serhii Nosko
                mikita_siadykh Mikita Siadykh
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases