Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluedart IGM (LSP)- Compliance Check #3171

Open
amitsinha07 opened this issue Jan 28, 2025 · 7 comments
Open

Bluedart IGM (LSP)- Compliance Check #3171

amitsinha07 opened this issue Jan 28, 2025 · 7 comments

Comments

@amitsinha07
Copy link

@desaisurajbd

@desaisurajbd
Copy link
Contributor

@amitsinha07 as we are logistics seller could you please share the logs of any live logistics BPP ?

@amitsinha07
Copy link
Author

@desaisurajbd

@desaisurajbd
Copy link
Contributor

@amitsinha07 please check updated logs in #3178 this PR

@amitsinha07
Copy link
Author

@desaisurajbd

On_issue

  • TTL = PT30S as per the API Contract.
  • message/issue/issue_actions/respondent_actions/[0]/updated_by/contact/phone - is not in the valid range.
  • message/issue/issue_actions/respondent_actions/[0]/updated_by/org/name - domain name is missing.

On_issue_status

  • TTL = PT30S as per the API Contract.
  • Context timestamp should be greater than or equal to message/issue/updated_at in on_issue_status.
  • message/issue/resolution_provider/respondent_info/type must be equal to one of the allowed values:
    • INTERFACING-NP
    • TRANSACTION-COUNTERPARTY-NP
    • CASCADED-COUNTERPARTY-NP
  • message/issue/issue_actions/respondent_actions/[0]/updated_by/contact/phone - is not in the valid range.
  • message/issue/issue_actions/respondent_actions/[0]/updated_by/org/name - is mismatched with the context/bbp_id.
  • message/issue/issue_actions/respondent_actions/[0]/updated_by/org/name-domain is mismatched with the context/domain.
  • message/issue/issue_actions/respondent_actions/[1]/updated_by/contact/phone - is not in the valid range.
  • message/issue/issue_actions/respondent_actions/[1]/updated_by/org/name - is mismatched with the context/bbp_id.
  • message/issue/issue_actions/respondent_actions/[1]/updated_by/org/name-domain is mismatched with the context/domain.
  • message/issue/issue_actions/respondent_actions/[1]/updated_by/contact/phone - is not in the valid range.
  • message/issue/resolution_provider/respondent_info/resolution_support/contact/phone - is not in the valid range.
  • message/issue/resolution_provider/respondent_info/resolution_support/contact/gros/0/contact/phone - is not in the valid range.
  • message/issue/resolution_provider/respondent_info/organization/org/name - domain name is missing.
  • Refund Amount for /on_issue_status should only be present when action type is REFUND.

@desaisurajbd
Copy link
Contributor

@amitsinha07 please find our remarks against each issue as resolved and for few added comments.
On_issue
TTL = PT30S as per the API Contract. - Resolved
message/issue/issue_actions/respondent_actions/[0]/updated_by/contact/phone - is not in the valid range. -Resolved
message/issue/issue_actions/respondent_actions/[0]/updated_by/org/name - domain name is missing. -Resolved

On_issue_status
TTL = PT30S as per the API Contract. -Resolved
Context timestamp should be greater than or equal to message/issue/updated_at in on_issue_status. -Resolved
message/issue/resolution_provider/respondent_info/type must be equal to one of the allowed values: -Resolved
INTERFACING-NP
TRANSACTION-COUNTERPARTY-NP
CASCADED-COUNTERPARTY-NP
message/issue/issue_actions/respondent_actions/[0]/updated_by/contact/phone - is not in the valid range. -Resolved
message/issue/issue_actions/respondent_actions/[0]/updated_by/org/name - is mismatched with the context/bbp_id. -Resolved
message/issue/issue_actions/respondent_actions/[0]/updated_by/org/name-domain is mismatched with the context/domain.- It would be bpp_id right ?
message/issue/issue_actions/respondent_actions/[1]/updated_by/contact/phone - is not in the valid range. -Resolved
message/issue/issue_actions/respondent_actions/[1]/updated_by/org/name - is mismatched with the context/bbp_id.- It would be bpp id right ?
message/issue/issue_actions/respondent_actions/[1]/updated_by/org/name-domain is mismatched with the context/domain. - Repeated
message/issue/issue_actions/respondent_actions/[1]/updated_by/contact/phone - is not in the valid range. -Resolved
message/issue/resolution_provider/respondent_info/resolution_support/contact/phone - is not in the valid range. -Resolved
message/issue/resolution_provider/respondent_info/resolution_support/contact/gros/0/contact/phone - is not in the valid range. -Resolved
message/issue/resolution_provider/respondent_info/organization/org/name - domain name is missing.- Domain name is there.
Refund Amount for /on_issue_status should only be present when action type is REFUND. -Resolved

@amitsinha07
Copy link
Author

@desaisurajbd

Please join the Daily 11 AM Community Call to discuss your doubts. You can also reach out via email at [email protected].

ONDC Tech Community Call (API Implementation - All Domains)
🗓 mon to friday
11:00 AM – 12:00 PM IST

Google Meet Details:
🔗 Join here: https://meet.google.com/bpo-pwwh-fja
📞 Dial-in (US): +1 347-389-1685‬ (PIN: 650 319 046#)
📞 More phone numbers: [Click here](https://tel.meet/bpo-pwwh-fja?pin=6443347012985)

@amitsinha07
Copy link
Author

@desaisurajbd

On_issue

TTL = PT30S as per the API Contract.

On_issue_status

TTL = PT30S as per the API Contract.

  • message/issue/id must match the format "uuid".
  • message/issue/issue_actions/respondent_actions/[0]/updated_at of the on_issue_status call should match with the message/issue/issue_actions/respondent_actions/[0]/updated_at of the on_issue call.
  • message/issue/issue_actions/respondent_actions/[0]/short_desc of the on_issue_status call should match with the message/issue/issue_actions/respondent_actions/[0]/short_desc of the on_issue call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants