-
Type:
Bug
-
Status: Implemented (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0-IP-2
-
Component/s: all
-
Labels:None
I reviewed the PrintTalk 2.0 spec and found many potential issues, but I am not sure about them and don't want to waste everyone's time with a bunch of Jira issues that get rejected.
It seems like the most efficient way to do this is to post an FDF (and the corresponding PDF), then Rainer can go through the comments, and for each, do one of the following:
- Add a reply explaining why everything is fine (in the case there is no issue)
- Add a reply saying what the fix is (in the case there is an issue, but it is easily fixed and does not justify having a separate issue; Graham can go through the resultant FDF and make these simple fixes after Rainer is done)
- Create a separate Jira issue, and add a reply with the resultant issue number
- causes
-
PTK-136 Rigidly define which business objects are referenced by BusinessRefID
-
- Rejected
-
-
PTK-130 update restriction of Request
-
- Implemented
-
-
PTK-131 clarify 3.7 OrderStatusResponse
-
- Implemented
-
-
PTK-132 update Quote/@DeviationFactor
-
- Implemented
-
-
PTK-133 Clarify the use of Estimate in RFQ, Quote and PO
-
- Implemented
-
-
PTK-134 Use of Pricing/Payment in the context of a StockLevel or RFQ
-
- Implemented
-
-
PTK-135 update figure A-3 status request cycle
-
- Implemented
-
- relates to
-
PTK-140 Revise workflow diagrams
-
- Rejected
-
-
PTK-139 Price/@Unit requires a list of values
-
- Implemented
-
-
PTK-142 Decide upon the cardinality of @Price
-
- Rejected
-
-
PTK-141 Create diagram for TBD in Structure introduction.
-
- Implemented
-