Related Feature
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Challenge | API | Release Version | Priority (P1-P5) | Comments | Identified by | JIRA Issue |
|---|---|---|---|---|---|---|
| Order date cannot be set in the past | /orders/composite-orders | P2 | Without this ability we cannot properly migrate current orders | Dennis Bridges | ||
...
| Challenge | API/Area of FOLIO | Release Version | Priority (P1-P5) | Comments | Identified by | JIRA Issue |
|---|---|---|---|---|---|---|
| It is currently hard to pin down the version of the schemas used in the Tenant. It would be great if the API:s could expose the json schemas . This would be very useful for creating mapping files, and validating data before migrating. As part of this, it would be great to have the referenced schemas in schemas either added as part of the schemas or at least make the links resolvable. Please ask it the last part is unclear. | All APIs that are using JSON Schemas | P3-P4... | ||||