Ekart - LSP - compliance check

[abhinavv245]

No description provided.

[sharique827]

Common Issue in all Flows

• Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
• /on_confirm/0/message/order/fulfillments/0/@ondc1org1awb_no should be 11-16 digits only",
• Must NOT have additional properties (bpp_terms tags) in on_status and on_cancel.
• Remove "error": null" from on_status payload.

Flow (Cancel-RTO)

• on_status call for order picked up and out-for delivery are missing.

Schema Errors

/on_cancel

• message/order/fulfillments/1 Must have required property end.
• message/order/fulfillments/1/start Must have required property location.

Message Errors

/on_Confirm

• order/updated_atcannot be future-dated with respect tocontext/timestamp`.

/on_cancel

• Pickup timestamp (fulfillments/start/time/timestamp) is missing for fulfillment state - Cancelled.

/on_status

• Pickup timestamp (fulfillments/start/time/timestamp) is missing for fulfillment state - Cancelled.
• fulfillments/end/time/timestamp is missing for RTO fulfillment with state - RTO-Delivered.

FLOW-2

Context Part

/on_status

• Message Id cannot be the same for different sets of APIs in all on_status call.

Message

/on_confirm

• order/updated_at cannot be future-dated with respect to context/timestamp.
• order/created_at cannot be future-dated with respect to context/timestamp.

Flow-3

Context Part

/on_cancel

• Message Id cannot be the same for different sets of APIs.

Message Part

/on_confirm

• order/updated_at cannot be future-dated with respect to context/timestamp.

/on_cancel

• order/created_at or order/updated_at should not be future-dated with respect to context/timestamp.

@tushar-jaiswal17