Support Portal

An issue that resulted in some days being repeated if a certain combination of template code was used has been fixed.  This impacted Planner 2.0 itineraries...

An issue that prevented all appropriate costs from displaying when certain combinations of cost category type section filters  (e.g., others&meals&t...

An issue that caused some costs to be duplicated or not appear when using a prefix filter (e.g., other.p15_name) within a cost category type section filter ...

An issue that occured when using a cost start destination placeholder (e.g., coststartdestination.p15_name) when there was a cost without a start destinatio...

An issue that caused an error to be thrown when a guest itinerary was using the status reason of a cost item (e.g., costitem.statuscode) and the user opted ...

An issue that caused html formatting in a text field to be not be translated because of the use of upper case in the html format command (e.g., p15_descript...

A feature gap between the current itinerary system and Planner 2.0 itineraries that didn't allow for fields from the departure client's contact reco...

An issue that resulted in text fields that contain line breaks not being rendered correctly has been fixed.  This impacted Planner 2.0 itineraries only.

An issue with usage of valuesrequired.begin/end with departure fields has been fixed.  This impacted Planner 2.0 itineraries only.

An issue that resulted when a cost item reservation had an invalid start time or time of day entered has been resolved.  This only impacted Guest Itineraries.