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

Added igm logs for Chalo #1835

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Added igm logs for Chalo #1835

wants to merge 3 commits into from

Conversation

g-arpit
Copy link

@g-arpit g-arpit commented Dec 10, 2024

No description provided.

@amitsinha07
Copy link

@g-arpit

Issue

Missing Required Properties:

  • message/issue/source.
  • message/issue/expected_response_time.
  • message/issue/expected_resolution_time.
  • message/issue/order_details/provider_id.
  • message/issue/issue_actions/complainant_actions/0/updated_by/contact/email.
  • message/issue/complainant_info/contact/email.
  • message/issue/source/network_participant_id.

TTL: Should be PT30S as per the API Contract.
BAP_ID and BPP_ID: Both are matching.

On_Issue

TTL: Should be PT30S as per the API Contract.
Missing Required Properties:

  • message/issue/created_at.
  • message/issue/updated_at.
  • message/issue/issue_actions/respondent_actions/0/updated_by/contact/email.

BAP_ID and BPP_ID: Both are matching.
message/issue/respondent_actions/org/name: Should match message/issue/complainant_actions/org/name in the Issue call.

Issue_Status

BAP_ID and BPP_ID: Both are matching.
TTL: Should be PT30S as per the API Contract.
Transaction ID mismatch: Between /issue and /issue_status.

On_Issue_Status

BAP_ID and BPP_ID: Both are matching.
message/issue/id: Should follow the UUID format.

Missing Required Properties:

  • message/issue/resolution_provider/respondent_info.

TTL: Should be PT30S as per the API Contract.
Transaction ID mismatch: Between /issue and /on_issue_status.

updated_at: The updated_at of message/issue/issue_action/respondent_actions/index[1]/updated_at should be same as or less than message/issue/updated_at in on_issue_status.
created_at: Should match the created_at from the Issue.

General Issues

All /email fields are missing in the payload:

  • message/issue/issue_actions/respondent_actions/0/updated_by/contact/email.
  • message/issue/issue_actions/respondent_actions/1/updated_by/contact/email.
  • message/issue/resolution_provider/respondent_info/organization/contact/email.
  • message/issue/resolution_provider/respondent_info/resolution_support/contact/email.
  • message/issue/resolution_provider/respondent_info/resolution_support/gros/0/contact/email.

@92shreyansh
Copy link
Member

@amitsinha07 Please also check the context of IGM as it should follow the base transaction context which in TRV11 is different

@92shreyansh 92shreyansh added the IGM Issue & Grievence Management label Dec 31, 2024
@g-arpit
Copy link
Author

g-arpit commented Jan 15, 2025

Regarding these 2 comments:

BAP_ID and BPP_ID: Both are matching. - This is because we are onboarded both as seller and buyer with same subscriber id.
TTL: Should be PT30S as per the API Contract. - Isn't setting TTL decision for the NP to take? I don't think so that it can be fixed for all the NPs.

@amitsinha07
Copy link

@g-arpit

Issue

  • message/issue/issue_actions/complainant_actions/0/updated_at should match the created_at.

Issue Status

  • Transaction ID mismatch in /issue and /issue_status.
  • message/issue/id must match the format "uuid".

On Issue Status

  • Transaction ID mismatch in /issue and /on_issue_status.
  • context/timestamp of the on_issue_status call should be greater than the context/timestamp of the issue_status call.

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

Successfully merging this pull request may close these issues.

3 participants