Proxtera - B2B - IGM (BA & SA) - compliance check #1850
Comments
BuyerFulfillmentIssuecontext/ttl: Is not as per the API contract. On_IssueThe updated_at of message/issue/issue_action/respondent_actions/index[0]/updated_at: Should be the same as or less than message/issue/updated_at in on_issue. Issue_Closecontext/ttl: Is not as per the API contract. On_Issue_Statuscontext.action: Should be "On_issue_status". ITEMIssuecontext/ttl: Is not as per the API contract. On_Issuecontext/timestamp: Should be greater than the context/timestamp from the issue call. On_Issue_Statuscontext.action: Should be "On_issue_status". Issue_Closecontext/ttl: Is not as per the API contract. Additional NotesNo Issue_Status Call is available. |
|
@amitsinha07 |
|
There is no new or updated document for IGM 1.0.0 and pls submit the logs once you had tested this with utility @srijit-prox |
@RupalSingla share the utility. https://ondc-official.github.io/ONDC-NTS-Specifications/#/Complaint%20lifecycle%20management/post_issue |
|
https://github.com/ONDC-Official/log-validation-utility. this is the link for the utility |
|
@amitsinha07 @RupalSingla we have fixed the issues and created a PR. Please look into it. |
Feedbacks for (Buyer & Seller)FullfillmentIssue
On Issue Status
ItemIssue
On Issue
On Issue Status
|
|
what is the correct format for these?
|
Duration Format SpecificationThe expected duration should follow the ISO 8601 Duration Format, commonly used for representing time intervals in a structured and standardized way. Examples include For reference, please consult the API Contract Documentation. ISO 8601 Duration Format Examples:
|
amitsinha07
changed the title
FulfillmentIssuemessage/issue/complainant_info/contract/email - is invalid. On_issuecontext/timestamp should be greater than the context/timestamp of the issue call. Issue_CLOSEmessage/issue/issue_actions/complainant_actions/0/updated_by/contract/email - is invalid. On_issue_status (Unsolicited)message/issue/issue_actions/complainant_actions/1/updated_by/contract/email - is invalid. ItemIssuemessage/issue/complainant_info/contract/email - is invalid. On_issuecontext/timestamp should be greater than the context/timestamp of the issue call. Issue_CLOSEmessage/issue/issue_actions/complainant_actions/0/updated_by/contract/email - is invalid. On_issue_status (Unsolicited)message/issue/issue_actions/complainant_actions/1/updated_by/contract/email - is invalid. |
@srijit-prox
Seller
Fulfillment
Issue
context/ttl: Is not as per the API contract.
created_at and updated_at[1]: Are mismatched in the issue call.
message/issue/expected_resolution_time: Is not as per the API contract.
message/issue/expected_response_time: Is not as per the API contract.
message/issue/complainant_info/contact/phone: Must not have more than 11 characters.
message/issue/complainant_info/contract/email: Is invalid.
message/issue/issue_actions/complainant_actions/0/updated_by/contract/email: Is invalid.
On_Issue
The updated_at of message/issue/issue_action/respondent_actions/index[0]/updated_at: Should be the same as or less than message/issue/updated_at in on_issue.
Issue_Close
context/ttl: Is not as per the API contract.
created_at: Is mismatched in the issue call.
message/issue/rating: Must be equal to one of the allowed values (THUMBS-UP, THUMBS-DOWN).
message/issue/complainant_info/contact/phone: Must not have more than 11 characters.
Phone Number for /issue_close API: Is not in the valid range.
message/issue/issue_actions/complainant_actions/0/updated_by/contract/email: Is invalid.
message/issue/issue_actions/complainant_actions/1/updated_by/contract/email: Is invalid.
On_Issue_Status
context.action: Should be "On_issue_status".
context/message_id: Should match between /on_issue and /on_issue_status.
message/issue/updated_at: Should be less than or equal to updated_at[1].
message/issue/issue_actions/complainant_actions/1/updated_by/contract/email: Is invalid.
message/issue/resolution_provider/respondent_info/resolution_support/gros/0/contact/email: Is invalid.
The updated_at of message/issue/issue_action/respondent_actions/index[0]/updated_at: Should be the same as or less than message/issue/updated_at in on_issue_status.
Additional Notes
No Issue_Status Call is available.
ITEM
Issue
context/ttl: Is not as per the API contract.
created_at and updated_at[1]: Are mismatched in the issue call.
message/issue/expected_resolution_time: Is not as per the API contract.
message/issue/expected_response_time: Is not as per the API contract.
message/issue/complainant_info/contact/phone: Must not have more than 11 characters.
message/issue/complainant_info/contract/email: Is invalid.
message/issue/issue_actions/complainant_actions/0/updated_by/contract/email: Is invalid.
On_Issue
context/timestamp: Should be greater than the context/timestamp from the Issue call.
The updated_at of message/issue/issue_action/respondent_actions/index[0]/updated_at: Should be the same as or less than message/issue/updated_at in on_issue.
On_Issue_Status
context.action: Should be "On_issue_status".
context/message_id: Should match between /on_issue and /on_issue_status.
message/issue/updated_at: Should be less than or equal to updated_at[1].
message/issue/issue_actions/complainant_actions/1/updated_by/contract/email: Is invalid.
message/issue/resolution_provider/respondent_info/resolution_support/gros/0/contact/email: Is invalid.
The updated_at of message/issue/issue_action/respondent_actions/index[0]/updated_at: Should be the same as or less than message/issue/updated_at in on_issue_status.
Issue_Close
context/ttl: Is not as per the API contract.
created_at: Is mismatched in the issue call.
message/issue/rating: Must be equal to one of the allowed values (THUMBS-UP, THUMBS-DOWN).
message/issue/complainant_info/contact/phone: Must not have more than 11 characters.
Phone Number for /issue_close: Is not in the valid range.
message/issue/issue_actions/complainant_actions/0/updated_by/contract/email: Is invalid.
message/issue/issue_actions/complainant_actions/1/updated_by/contract/email: Is invalid.
General Observation
There is no Issue_Status call.
The text was updated successfully, but these errors were encountered: