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 to use item assignments, has been fixed. This issue only impacted Guest Itineraries.
Itinerary: Cost Item status reason placeholder when generating a guest itinerary that uses item assignments issue Print
Modified on: Thu, 29 Sep, 2022 at 5:31 AM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.