Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
-
ERM Sprint 159, ERM Sprint 160, ERM Sprint 161, ERM Sprint 162, ERM Sprint 163, ERM Sprint 164, ERM Sprint 165, ERM Sprint 167, ERM Sprint 168, ERM Sprint 169, ERM Sprint 170, ERM Sprint 171, ERM Sprint 173, ERM Sprint 174, ERM Sprint 175
-
Bienenvolk
-
Poppy (R2 2023)
-
TBD
Description
Purpose/Overview:
To support a "push" model for getting data into the Agreements local KB from an external data source, implement a new endpoint that will support a "push" process.
This is to give us an option to externalise the data synchronisation process and therefor have more flexibility about how and where we manage data sync tasks in Agreements
Includes work to have appropriate schemas supported for the 'pushed' data and the processing of the data appropriately on the mod-agreements side. This will be processing "PCI" level data (so from a granular level)
Will need to know:
- How many PCI based objects will be accepted per request to the endpoint
- What responses are required from the endpoint to the "push" process and under what circumstances
TestRail: Results
Attachments
Issue Links
- defines
-
ERM-2650 mod-agreements release. Fix version: 6.0.0 (Poppy)
-
- Closed
-
-
-
- Closed
-
-
UXPROD-3886 Support 'push' based mechanism for populating Agreements Local KB
-
- Closed
-
- has to be done before
-
-
- In progress
-
- relates to
-
ERM-2791 Simplification of package status handling
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1.
|
Refactor title ingest |
|
Closed | Ethan Freestone |
2.
|
Refactor package ingest |
|
Closed | Ethan Freestone |