Skip Navigation

com.sabre.redapp.example3.desktop.pricing.qualifiers Sample

This sample demonstrates how you can intercept and modify pricing qualifiers like:

  • Account Codes

  • Corporate ID’s

  • Retailer Rule Qualifiers

  • Commission Codes

  • Brand ID’s (per segment id)

  • Segment Select

  • Booking Class (only during "Sell & Save Price" flow)

  • Validating Carrier

  • Tour Codes

  • Endorsements

  • Discounts

  • Commissions

  • Form of Payment

  • Special Penalty Info

  • Air Pricing Info (only during "Sell & Save Price" flow)

This sample also demonstrates possibility to override core price command WP by FP (aka Future Pricing) for example. Be aware that override of the core WP pricing command is not validated by the framework so any text passed by RedApp code will be intercepted and utilized.

There are several ways you can trigger extension points in Air Pricing flows:

  1. Basic pricing is triggered by WP.* commands. When such command is sent, then sample application’s service registered to the dynamo.air.pricing:beforePricingRequest extension point triggers a graphical input form to allow agent modify/remove/add qualifiers to the RedAppAirPriceRQ Red App model. Once this is completed, air pricing logic will utilize those qualifiers.

  2. Advanced pricing is triggered from GUI, it will be executed in any sequence leading the user to sending an air pricing request from the "Advanced Pricing" modal window, e.g.: Air Availability (graphical form) → Search Availability button → Sell button → Pricing Options button → Advanced Pricing Options option → Price button; the "Advanced Pricing" modal window may also be triggered from the 'Trip Summary' helper tool in the side panel (click on the ellipsis icon in air segment, then choose the 'Price' option). When Air Pricing request is triggered, the sample application’s service registered to the dynamo.pricing.advanced:beforePricingRequest extension point triggers a graphical input form to allow agent modify/remove/add qualifiers to the RedAppAirPriceRQ Red App model. Once this is completed, air pricing logic will utilize those qualifiers.

  3. Pricing exectued during the "Sell & Save Price" action. When the Sell & Save Price button is used, then sample application’s service registered to the dynamo.air.airbooking:beforePricingRequest extension point will add additional pricing qualifiers to the RedAppAirShoppingRq Red App model. Once this is completed, air pricing logic (executed just after the "Sell & Save Price" action is triggered) will utilize those qualifiers.

Form displayed during air pricing
Figure 1. Form displayed during air pricing
Form displayed during "Sell & Save Price"
Figure 2. Form displayed during "Sell & Save Price" (a)
Form displayed during "Sell & Save Price"
Figure 3. Form displayed during "Sell & Save Price" (b)
Note
 The above features work in Sabre Red 360 only. In SRW 2.0 they do not apply.