Digiledge (IGM) - compliance check

[Rishabh-ondc]

issue

• context.core_version should be 1.0.0
• issue.description.additional_info need not be sent if empty
• complainant_actions.updated_by.org.name should have the info as "subscriber_id::domain"

on_issue

• context.core_version should be 1.0.0
• context.ttl should not be there
• domain code of respondent_actions.updated_by.org.name should ideally match with the context domain code

issue_status

• context.core_version should be 1.0.0
• context.transaction_id is same as issue/on_issue call

on_issue_status

• context.core_version should be 1.0.0
• context.ttl should not be there
• domain code of respondent_actions.updated_by.org.name for "PROCESSING" should ideally match with the context domain code
• attributes in respondent_actions should be of the seller app which is the respondent for "RESOLVED" action
• respondent_actions.updated_at seems very different from context.timestamp
• resolution_provider.respondent_info.organization.org.name should be of the seller providing the resolution
• resolution_provider.respondent_info.resolution_support.chat_link may not be sent if not available. Placeholder values are provided as of now

issue close

• context.core_version should be 1.0.0
• complainant_actions.updated_by.org.name should have the info as "subscriber_id::domain"
• issue.rating should ideally be captured for log illustration

Clarifications

• Please illustrate logs with another NP or with the reference buyer/ seller app
• Please share 2 logs, one for "ITEM" category and one for "FULFILLMENT" category

@shabirahamed

[Rishabh-ondc]

Flow 1 on_issue

• API call is timestamped after more then 6 hours, much later than the expected response time, please check

on_issue_status

• timestamps are much before than the time of the complaint
• respondent_info.gros.gro_type should be TRANSACTION-COUNTERPARTY-NP-GRO
• issue.updated_at has not changed

Flow 2 issue

• issue.created_at and updated_at should have three milliseconds in the timestamp

on_issue

• issue.created_at should have three milliseconds in the timestamp
• API call is timestamped after more than 5 hours, much later than the expected response time, please check

issue cascaded

• All timestamps are mismatching

Clarification

• Flow 1; peson.name, description.short_desc and long_desc are provided as missing, Please check
• Please illustrate logs with another NP whose logs have been verified or with the reference buyer/ seller app
• Please illustrate both the scenarios (Scenario 2 and Scenario 3) for on-network logistics as mentioned in the test scenarios

@shabirahamed

[Rishabh-ondc]

Flow 1 on_issue_status

• respondent_info.contact and person is changing across actions. Please check.

Flow 2 issue cascaded

• Is the same transaction_id beind used across retail and logistics flows?

on_issue_status

• message_id should be different from on_issue_status_cascaded
• gros object should also capture the gro information of the seller app (transaction-counterparty-np-gro)

Clarifications

• Ideally there should be an on_issue_status call between on_issue_cascaded call and on_issue_status_cascaded call informing that the LSP is now processing the complaint
• Issue close call should also be cascaded to the LSP as well and log of the same is to be shared

Flow 3

• same as above

on_issue_status

• context.timestamp of on_issue_status is less than context.timestamp for on_issue_status_casaded

Clarifications

• In Flow 3, seller app should be providing a resolution that is different to the LSP's resolution and then the seller app should become the resolution provider

General clarifications

• Please illustrate logs with another NP whose logs have been verified or with the reference buyer/ seller app

@shabirahamed

[Rishabh-ondc]

Flow 2 on_issue_status unsolicited

• issue.updated_at should not change as there is no change done by the seller app

on_issue_status resolved

• issue.updated_at should not change as there is no change done by the seller app

issue close cascaded

• issue.updated_at and respondent_actions.updated_at should not change

Flow 3 on_issue_status unsolicited

• issue.updated_at should not change as there is no change done by the seller app

issue close cascaded

• issue.updated_at and respondent_actions.updated_at should not change

General clarifications

• Illustrate logs with another NP whose logs have been verified or with the reference buyer/ seller app
• Use actual/ near actual values for contact.phone and email

@shabirahamed

[Rishabh-ondc]

Flow 2 issue cascaded

• issue.updated_at has not changed

issue close closed

• issue.updated_at and respondent_actions.updated_at should not change

Flow 3

• same as above

on_issue_status_resolved

• issue.updated_at timestamp is not as per standard format, only two decimal places provided

General Clarifications

• Use actual/ near actual values for contact.phone and contact.email
• Logs for seller side have been shared and the same is being reviewed. For buyer side, please share separate logs if buyer app's logs are to be verified as well

@shabirahamed

[Rishabh-ondc]

Seller App IGM logs cleared

@shabirahamed