awards_and_contracts.md: update purchase orders example #1720
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #1694
I've retained using csv table examples rather than json as I think it helps to see the values in a table format. The new example isn't a very good one for double counting risk as the initial contract has a
maximumValue
rather than a fixedvalue
so as well as a table showing the initial contract and one showing the purchase ordertransactions
I've also included a third example which shows how putting it all inContract.value
could lead to double counting.