Release confirmation partial success

[Azurab]

An optional step in after sale process: release (dedicated for bookings that allocates some resources like reservations) similar to fulfillment step in a booking process (but in "opposite way": it confirms releasing instead of holding some resources) is associated with a partial success problem.
How does OSDM handle complicated case when a FulfillmentId requested in POST release-offer action has reservations allocated in many resources and some of them are released but others are not at release-offer confirmation step (action PATCH release-offer/{releaseOfferId})?
Can a fulfillment have more than one release offer (one releaseOfferId for each fulfillmentPart)? I guess not, because entire fulfillmentId must be clearly valid or cancelled from traveler point of view.

[jspetrak]

Hello,

there is actually releaseSpecifications array in the ReleaseOfferRequest. That way, you can not only specify the entire Fulfillments to be released, but also drill down to individual BookingParts (Admission, Reservation, Ancillary).

In the refund, we have already removed fulfillmentIds from the actionOfferRequest. Specification can support both complete or partial action. Exchange and Release will be aligned in OSDM 4.0.

Booking also has releaseOffers as an array so you can have multiple releases running in the same time.

[Azurab]

Hi, thank you.
In releaseSpecifications I can see that fulfilmentId has notEmpty property and in my opinion that is good.
I am just wondering how the purchaser can be left with a half released fulfilment. The only thing I can see is to prvide new fulfilment without released offerParts.