-
Notifications
You must be signed in to change notification settings - Fork 16
EBL 3.0: SD-2502: Add shippingInstructionsRevisionNumber to SI #578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3055,6 +3055,11 @@ components: | |
| The `Shipping Instructions` is an enrichment to the original booking shared by the Shipper to the Carrier. The information given by the Shipper through the `Shipping Instructions` is the information required to create a `Draft Transport Document`. | ||
| title: Create Shipping Instructions | ||
| properties: | ||
| shippingInstructionsRevisionNumber: | ||
| type: integer | ||
| description: | | ||
| The version number of the **Shipping Instructions** provided by the customer to ensure the carrier uses the most recent update when creating the **Transport Document**. This value is expected to increment by one with each **Shipping Instructions** update, with higher values representing newer versions. | ||
|
Comment on lines
+3058
to
+3061
|
||
| example: 1 | ||
| transportDocumentReference: | ||
| type: string | ||
| pattern: ^\S(?:.*\S)?$ | ||
|
|
@@ -3371,6 +3376,11 @@ components: | |
| description: | | ||
| The identifier for a `Shipping Instructions` provided by the carrier for system purposes. | ||
| example: e0559d83-00e2-438e-afd9-fdd610c1a008 | ||
| shippingInstructionsRevisionNumber: | ||
| type: integer | ||
| description: | | ||
| The version number of the **Shipping Instructions** provided by the customer to ensure the carrier uses the most recent update when creating the **Transport Document**. This value is expected to increment by one with each **Shipping Instructions** update, with higher values representing newer versions. | ||
| example: 1 | ||
| transportDocumentReference: | ||
| type: string | ||
| pattern: ^\S(?:.*\S)?$ | ||
|
|
@@ -3688,6 +3698,11 @@ components: | |
| description: | | ||
| The identifier for a `Shipping Instructions` provided by the carrier for system purposes. | ||
| example: e0559d83-00e2-438e-afd9-fdd610c1a008 | ||
| shippingInstructionsRevisionNumber: | ||
| type: integer | ||
| description: | | ||
| The version number of the **Shipping Instructions** provided by the customer to ensure the carrier uses the most recent update when creating the **Transport Document**. This value is expected to increment by one with each **Shipping Instructions** update, with higher values representing newer versions. | ||
| example: 1 | ||
| transportDocumentReference: | ||
| type: string | ||
| pattern: ^\S(?:.*\S)?$ | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
shippingInstructionsRevisionNumberfield lacks constraints. Consider addingminimum: 1to ensure the revision number is always positive, as the description indicates it increments starting from 1.