Uploaded image for project: 'mod-orders'
  1. mod-orders
  2. MODORDERS-615

Define and implement CRUD Business API for acquisition method

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Won't Do
    • None
    • None
    • None

    Description

      Overview

      Support EDI export configuration by account: See the API wiki for details : https://wiki.folio.org/display/ACQ/Export+FOLIO+orders+in+EDIFACT+format#ExportFOLIOordersinEDIFACTformat-Addtableschemaforexportconfigurations,CRUDandAPI(mod-organizations)

      Approach

      1. Define the API (RAML, ModuleDescriptor)

      * CRUD API /orders/acquisition-methods/

      2. Implement the API
      3. Delete must be forbidder if exist configuration for EDIFACT orders export

      Acceptance Criteria

      API is defined and implemented
      Unit tests are updated

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-531 Export FOLIO orders in EDIFACT format

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            has to be done after

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEXPS-40 Create schema to support EDI order export functionality

            • 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. MODORDSTOR-258 Define and implement CRUD Storage API for acquisition method

            • 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. UIOR-846 Create area Settings->Orders->Acquisition methods

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-852 Select Acquisition method from controlled vocabulary list

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIPFPOL-33 Select 'Acquisition method' filter from controlled vocabulary list

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

            Activity

              People

                Unassigned Unassigned
                Andrei_Makaranka Andrei Makaranka
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases