| Lost password | Request login credentials

Knowledgebase: Database/Operations
Partial Allocation and Automessaging
Modified on 13 December 2012 01:46 PM

A Tourplan system set up to work with Automessaging functionality does not have a specific Tab to work with services that are to hold Partial Allocation. The system has always set service status to be Initial Request Service Status which would prompt a Request message to the Supplier to be sent for the entire service.

What may have not been obvious in version prior to 2.07 is that when a service does not have full Allocation available Tourplan will refer to the service status that is set in the "Unavailable" tab for "Request changed to Waitlist". This is because there is no specific Tab to work with Partial Allocation.

The service status defined against "Request Changed to Waitlist" is important for systems on version 2.07. If the service status is defined in Codemaint to not be included in the booking total then Automessaging will not be activated on this service status. With the new functionality for Optional Services the system will not Automessage any service line that has a service status that is set to not be included in the total. The logic being that these services are alternative or additional in the booking and messaging should not be automatic.

We have a white paper that will help you to …

  • Understand how to work with functionality that impacts this area with changes made in version 2.07+
  • Set up database to work with Partial Allocation when also using Automessaging

To access this white paper click here...

(0 vote(s))
Not helpful

Comments (0)