ONDC-Official/v1.1.0-logs

n-store (IGM) - compliance check

Opened this issue · 5 comments

RupalSingla commented

Flow 1
/issue

  • /context must have required property 'ttl'

/on_issue

  • The 'updated_at' of message/issue/issue_action/respondent_actions/index[0]/updated_at should be the same as 'message/issue/update_at' in on_issue
  • 'created_at' should match issue's 'created_at'

/issue_status

  • /context must have required property 'ttl'
  • /message/issue_id must match format "uuid"

@sathish

nstoretech commented

@RupalSingla I have updated the logs please review it.

PR - #723

RupalSingla commented

Flow 2:
1 /issue

  • /context must have required property 'ttl

2 /on_issue

  • updated_at": "The 'updated_at' of message/issue/issue_action/respondent_actions/index[0]/updated_at should be the same as 'message/issue/update_at' in on_issue",
  • "created_at": "'created_at' should match issue's 'created_at'"

3 /on_issue_status

  • schemaErr0": "/message/issue/id must match format "uuid"",
  • "igmIssueMsgId": "Message ID mismatch in /issue_status and /on_issue_status",
  • "org_name": "Organization's Name for /on_issue_status api in message/issue/issue_actions/respondent_actions/[3] mismatched with BAP ID",
  • "updated_at": "The 'updated_at' of message/issue/issue_action/respondent_actions/index[3]/updated_at should be the same as 'message/issue/update_at' in on_issue_status",
  • "created_at": "'created_at' should match issue's 'created_at'"

4 /on_issue_status_unsolicited

  • "schemaErr0": "/message/issue/id must match format "uuid"",
  • "igmTxnId": "transaction ID should not matched in /issue and /on_issue_status(unsolicited)",
  • "org_name": "Organization's Name for /on_issue_status api in message/issue/issue_actions/respondent_actions/[2] mismatched with BAP ID",
  • "updated_at": "The 'updated_at' of message/issue/issue_action/respondent_actions/index[2]/updated_at should be the same as 'message/issue/update_at' in on_issue_status",
  •         "created_at": "'created_at' should match issue's 'created_at'"

5 /lsp_issue

  • "org_name": "Organization's Name for /issue api mismatched with bap id",
  • "updated_at": "The 'updated_at' of message/issue/issue_action/complainant_actions/index[0]/updated_at should be the same as 'message/issue/update_at' in issue"

Flow 3 - Seller app should be providing the resolution

@sathish

Rishabh-ondc commented

Flow 2
ret_on_issue_status(Resolution)

  • respondent_info.type has changed
  • respondent_info.organization.org.name has changed

Clarifications

  • unsolicited on_issue_status should be initiated, please check

Flow 3
ret_on_issue_status(Resolution)

  • resolution provided same as provided by LSP; this can change if the seller app wants to change the resolution; please check

@sathish

nstoretech commented
  • resolution provided same as provided by LSP; this can change if the seller app wants to change the resolution; please check

  1. For Flow -2 respondent_info.type and respondent_info.organization.org.name will change and resolve this

  2. We are already sending unsolicited on_issue_status(Resolution) which was not added in the log.

  3. For the Resolution update, we have the option to change the LSP resolution using the JIRA tool to change the option.