Protean - LSP - compliance check

[abhinavv245]

All flows

/on_search

• for item with id 'Standard', time/timestamp should be relative to the context timestamp as per TAT.

/on_init

• @ondc/org/item_id ('Express') in quote/breakup does not match to items/id ('Standard')

/confirm

• What terms is BAP agreeing to? as BPP did not send terms

/on_update

• why are two shipping labels provided in start/instructions/images
• start/instructions/short_desc cannot be updated by LSP

/on_status

• vehicle.registration is assigned & remains the same after order reaches destination (in different state): means?
• Delivery timestamp (fulfillments/end/time/timestamp) cannot be future dated w.r.t context/timestamp for fulfillment state - Order-delivered (deferred flow)

RTS Flow

/search

• gps location is for Bangalore, area code is for Mumbai in start location?

/on_search

• how is LSP providing P2P options, area codes are for Mumbai and Bangalore

track and on_track

• tracking to be implemented for hyperlocal

@RaviV-Protean

[abhinavv245]

All Flows

/on_search

• For Immediate Delivery, TAT date should be the same date i.e. 2024-10-01 ( in /items )
• /on_search/0/message/catalog/bpp~1providers/0/items/0/time/timestamp must match format \"date\""

/on_confirm

• why are bpp_terms being sent in /on_confirm and not in /on_init (also these terms are not enabled yet, need not be sent)
• weight is updated in /confirm, is the LSP quoting the same price?

/on_status

• why is status call required everytime to send fulfillment state updates, they should be unsolicited.

@RaviV-Protean

[abhinavv245]

P2H2P Flow

/on_update

• shipping label is mandatory, to be sent in fulfillments/start/instructions/images for P2H2P Flow

@RaviV-Protean

[abhinavv245]

P2H2P Flow

/on_update

• why are two shipping labels provided in start/instructions/images?

Please fix this.

For now clearing logs for v1.2.

@JitendraD-Protean