Thunderjet - Spikes / Investigations

Feature level Designs should be added under Technical Designs and Decisions; the corresponding links should be added to the table below
Spikes and investigations should be added as child pages under Thunderjet - Spikes / Investigations; the corresponding links should be added to the table below


MODINVOICE-125 - Getting issue details... STATUS
MODINVOICE-101 - Getting issue details... STATUS	Spike: Investigate high memory usage
MODFISTO-34 - Getting issue details... STATUS	Spike: Avoiding partially paid invoices POC
	Prorated Invoice Adjustments
	Investigation: mod-orders/mod-orders-storage performance
	Finance Data Model
	Central File/Object Storage (WIP)
	Acquisition Units
UIORGS-81 - Getting issue details... STATUS
UINV-30 - Getting issue details... STATUS	Attaching Documents to Invoices
MODORDSTOR-89 - Getting issue details... STATUS	Spike: Investigate data migration strategies
UIORGS-61 - Getting issue details... STATUS	Spike: [UIORGS-61] Figure out if we are able to show error messages with a link
UIOR-190 - Getting issue details... STATUS	Spike: [UIOR-190] figure out the best option of i-scroll/pagination to use within MCL component
UIOR-156 - Getting issue details... STATUS	Spike: [UIOR-156] Leveraging the existing create item/holding forms from orders/receiving
MODORDSTOR-37 - Getting issue details... STATUS	Should first/last in collections be 0-based or 1-based?
MODORDSTOR-34 - Getting issue details... STATUS	Postgres SEQUENCEs for generating po_line_number suffixes
MODORDERS-125 - Getting issue details... STATUS
MODORDSTOR-34 - Getting issue details... STATUS	Postgres SEQUENCEs for generating po_line_number suffixes
UIV-63 - Getting issue details... STATUS
MODGOBI-34 - Getting issue details... STATUS
MODORDERS-80 - Getting issue details... STATUS
MODORDERS-106 - Getting issue details... STATUS	Spike: Guarantee of the PO Line status up-to-date
MODEXPW-40 - Getting issue details... STATUS	Details in the Jira ticket