Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
ACQ Sprint 128
-
1
-
Thunderjet
-
Lotus R1 2022
Description
Purpose/Overview:
To support configure EDIFACT export details per account, we need to separate EDI config from organization level.
Requirements/Scope:
- Remove EDI configuration from organization record to separate configuration model
- Save the configuration in a separate table
Approach:
1.
1.1. Copy field "edi" from ramls/acq-models/mod-orgs/schemas/organization.json to separate model "account_orders_export_config.json" and place in in the swagger.api/schemas/acquisitions.
1.2. Add schema "vendor_edi_orders_export_config.json" as option parameter to swagger.api/schemas/exportTypeSpecificParameters.json
1.3. Remove field "edi" from ramls/acq-models/mod-orgs/schemas/organization.json. Also store reference on the organization to which account is connected.
1.4. Verify that all needed information in the configuration is present
Acceptance criteria:
- New model with samples defined
- Table created
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-531 Export FOLIO orders in EDIFACT format
-
- Closed
-
- has to be done before
-
MODORDERS-615
Define and implement CRUD Business API for acquisition method
-
- Closed
-
-
MODORDSTOR-258
Define and implement CRUD Storage API for acquisition method
-
- Closed
-
-
UIOR-884
Re-export order via export
-
- Closed
-
-
UIOR-1034
Use Orders Export History API (mod-orders)
-
- Closed
-
-
UIORGS-271
Create details - Organization record can contain multiple "Integration details" configurations
-
- Closed
-
-
UIORGS-274
View details - Organization record can contain multiple "Integration details" configurations
-
- Closed
-
-
UIORGS-280
Remove EDI configuration from organization record
-
- Closed
-