Addble (IGM) - compliance check
Opened this issue · 3 comments
FLOW 1
/issue
- 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
- Time of creation and time of updation for /issue api should be the same
/on_issue
- Message ID mismatch in /issue and /on_issue
/issue_status
- /message must have required property 'issue_id'
- context.action should be issue_status
/on_issue_status
- Message ID mismatch in /issue_status and /on_issue_status
- The 'updated_at' of message/issue/issue_action/respondent_actions/index[1]/updated_at should be the same as 'message/issue/update_at' in on_issue_status
FLOW 2
/issue
- 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
- Time of creation and time of updation for /issue api should be the same
/on_issue
- Message ID mismatch in /issue and /on_issue
/issue_status
- /message must have required property 'issue_id'
- context.action should be issue_status
/on_issue_status
- Message ID mismatch in /issue_status and /on_issue_status
- The 'updated_at' of message/issue/issue_action/respondent_actions/index[1]/updated_at should be the same as 'message/issue/update_at' in on_issue_status
FLOW 3
- need to send close issue api for LSP to SNP
@RupalSingla
/issue - is coming from Reference Buyer App, We have no control on it.
/issue_status - reference buyer app was not sending this, so my submission does not have this payload. We are sending unsolicited /on_issue_status
For /on_issue_status
The 'updated_at' of message/issue/issue_action/respondent_actions/index[1]/updated_at should be the same as 'message/issue/update_at' in on_issue_status - this is not necessary I believe as long as the respondent_action and updated_atare in accordance. So in our case you will see that the respondent_actions payload for "respondent_action": "RESOLVED", has the correct timestamp.
For FLOW 3
Do I still need to resubmit or getting this implemented will be good enough?
@RupalSingla - can you please review the fixes?
Logs cleared for the submitted flows.