Uploaded image for project: 'ui-orders'
  1. ui-orders
  2. UIOR-884

Re-export order via export

    XMLWordPrintable

Details

    Description

      Overview:

      Each organization record may include multiple Integration detail configurations. These are essentially different export configurations. Organizations can also include multiple account numbers. For each organization the library should be able to associated each account number with 1 integration configuration.

       

      We need to show Re-send button only of particular order line id alredy had some exports before

      Scenarios:

             

      1. Scenario
        • Given user opens order action menu
        • When options are displayed in menu
        • Then Re-export appears in the list
      2. Scenario
        • Given manualPO is true
        • When Re-export action is shown in menu
        • Then it is inactive and user can not click on it
      3.  Scenario
        • Given user is intercepted by "re-export" confirmation modal
        • When re-export message is displayed
        • Then (Vendor name from export) is replaced with the name and code of the organization the order was previously exported to
        • AND (Integration method) is replaced by the name of the integration configuration used for the last export of this order
        • AND (Vendor name from order) is replaced by the name and code of the organization that is currently referenced in this purchase order
      4. Scenario
        • Given user is intercepted by "re-send" confirmation modal
        • When user clicks Confirm
        • Then order IS exported again with the next scheduled export to which it is assign (eg. EDI 1)
      5. Scenario
        • Given user is intercepted by "re-send" confirmation modal
        • When user clicks Cancel
        • Then open order operation is not attempted

       

      Notes for developers:

      1. Re-send includes setting lastEdiExportDate to null and pick up all suitable orders during next scheduled export jobs.  

      2. Need to rename button 'Resend' to 'Reexport'.

       

      SN: Is this button should be run on order-line level?

      This Reexport setting should appear on both PO and PO Line level

      If user clicks on PO level - UI will fetach all associated PO Lines and update lastEdiExportDate to null

      If user clicks on PO Line level - UI will update particular PO Line with  lastEdiExportDate to null

      For now in popup we can omit Integration method,  Vendor from Order, Vendor from Export. These changes will be done in scope of story: https://issues.folio.org/browse/UIOR-882 

       

      We should show Reexport Button on Order level when

      • Order is opened
      • Order has exported lines
      • On Order level when Manual set to false

      We should show Reexport Button on Order Line  level when

      • Order is opened
      • Order has exported lines
      • Order line automatic export set to true

      TestRail: Results

        Attachments

          Issue Links

            clones

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORGS-271 Create details - Organization record can contain multiple "Integration details" configurations

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

            New Feature - New feature requests UXPROD-3498 Allow user to Download or resend EDIFACT order exports

            • P2 - normal priority level, must be included in the current development cycle
            • 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. MODEXPW-43 Add step to save orders in EDIFACT format in the Minio object storage

            • 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. MODORDERS-783 Implement Orders Export History API

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-1034 Use Orders Export History API (mod-orders)

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

            Task - A task that needs to be done. FAT-3125 Review of C365612

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. FAT-3131 Review of C365618

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. FAT-3134 Review of C365619

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. FAT-3135 Review of C365621

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. FAT-3136 Review of C365622

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIEXPMGR-25 Third pane view - Search and filter organization exports logs

            • 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. UIEXPMGR-26 Search and filter organization exports logs

            • 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. UIOR-371 Allow user to set Acq method EDIFACT export triggers for POL

            • 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. UIOR-882 Display export details accordion for exported order lines

            • 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. UIOR-883 Filter orders lines by export date

            • 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. UIOR-886 Display export details on ORDER view

            • 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. UIORGS-269 Allow user to choose Acq method EDIFACT export triggers for each organization

            • 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. UIORGS-270 View organization exports action

            • 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. UIORGS-279 Display integration configuration view

            • 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. UIPFPOL-38 Filter orders lines by export date

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

            Activity

              People

                dennisbridges Dennis Bridges
                dennisbridges Dennis Bridges
                Dennis Bridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases