🧪 Experimental KB — Official knowledge hub: community.kaptio.com

Passenger Allocations Limited to 1 on Transfers with 'vehicle(s)' UOM

When using the passenger allocations screen for transfer services, only 1 passenger can be allocated to the item, regardless of how many passengers are on the itinerary or what the Max Unit Occupants

passenger-allocations transfers UOM price-category bug

Problem

When using the passenger allocations screen for transfer services, only 1 passenger can be allocated to the item, regardless of how many passengers are on the itinerary or what the Max Unit Occupants setting allows on the price category.

What We Found

The system does not correctly support the ‘vehicle(s)’ Unit of Measure (UOM) on price categories. Instead of allowing allocations up to the Max Unit Occupants limit, it restricts to only 1 allocation. This affects both the builder (default occupancy always 1) and the passenger allocations component. The issue was tracked as CEE-255 and fixed in version 20.3.12.

Solution

  1. Check the price category on the affected itinerary item - if UOM is ‘vehicle(s)’, this is the cause
  2. Permanent Fix: Upgrade to Kaptio version 20.3.12 or later (installation link available from support)
  3. Workaround: Change the Unit of Measure on the price category from ‘vehicle(s)’ to ‘unit(s)’
  4. Note: Changing UOM on price category immediately reflects on all related itinerary items (formula field Unit Type), builder display, costings, and resolves the passenger allocation issue
  5. Mass updates of UOM on price categories are safe and have no negative impact on existing itineraries

Notes

  • This issue only affects price categories with UOM set to ‘vehicle(s)’
  • The ‘unit(s)’ UOM does not have this limitation
  • After upgrading to 20.3.12+, ‘vehicle(s)’ UOM will work correctly and respect Max Unit Occupants
  • The fix allows allocating as many passengers as Max Unit Occupants allows; if empty, any number of allocations is allowed

Warnings

⚠️ If changing UOM as workaround, verify this doesn’t conflict with other business rules or reporting requirements for your org


Source: KHELP-11688

Was this article helpful?