-
Notifications
You must be signed in to change notification settings - Fork 0
OTST_TS_SNCF_EXCHANGE_EXCH_01
Scenario with an offer request based on a trip specification for a passenger, booking request based on the response of the offer response. The booking will be fulfilled with status confirmed. Exchange the booking for another route. The trip is based on a single outbound leg.
1.Generate and send a post offer request with a trip specification
2.Generate and send a post booking request
3.Generate and send a post fulfillment request
4.Generate and send a get booking request
5.Generate and send a post exchange offers request
6.Generate and send a post exchange operations request
7.Generate and send a post fulfillment request
8.Generate and send a get booking request
TBD
Step 1 to 4: same validation as made in the Offer/Book/Ticket scenario Step 5:
- ExchangeFee / amount
- exchangePrice / amount
- fulFillments
- offerID
Step 6:
- Status PREBOOKED
Step 7:
- Status : FULFILLED
Step 8:
- Validate the price comparing the ExchangeFee and ExchangePrice (Fees amounbt calculated based on the exchange condition related to the choosen offer)
- ExchangeOffers / ExchangeFee / Amount
- ExchangeOffers / ExchangePrice / Amount
- Home
- Meeting Minutes
-
SFRs
- OTST_TS_OB_RFND_01 : Full Refund Happy Flow
- OTST_TS_OB_RFND_02 : Full Refund Payment_Failure
- OTST_TS_OB_RFND_03 : Full Refund CODE_DOES_NOT_EXIST
- OTST_TS_OB_OFER_01 : Generic Offer display & validation
- OTST_TS_OB_RFND_05_Generic_Reason_Code
- SFRs WIP
- OTST_TS_OB_BOOK_01
- OTST_TS_OB_MULTI_LEG_1
- OTST_TS_OB_MULTI_PAX_1
- OTST_TI_FULFILLMENT_Enhancement
- OTST_TS_SNCF_PAX_INFO_UPD
- OTST_TS_SNCF_EXCHANGE_EXCH_01
- Night Trains
- SSDs
- ALTEN‐UIC‐SSD‐OTST_TS_OB_OFFER
- ALTEN‐UIC‐SSD‐OTST_TS_OB_RFND