Learning & Training sessions

Executed the test cases and reviewed the admin module, becoming familiar with each module covered in the introductory class.

Gopika Shaji wrote in #note-3:

Executed the test cases and reviewed the admin module, becoming familiar with each module covered in the introductory class.

Executed the test cases and reviewed the admin module, familiarizing myself with the various actions and booked statuses covered in the class.

Went through the test cases up until the customer detail page, familiarized myself with the admin module, and reviewed each tab. And also I attended the second review meeting.

Noticed some server errors and technical issues while trying to make blank bookings in the Insurance, Activities, and Transfer modules on the Maquaam site. I’ve reported these problems to Nidheesh.

Reported some issues in Maqam and also attended a class about inventory management.

Reported issues:- Bug #20200 Flight| Add baggage and meal not displaying issue

become familiar with admin side of attar travels

Getting familiar with the admin actions like SYNC PNR, Retrieve pnr, retrieve ticketing executed each of them with different scenarios

Reported issues:-Bug #20481 Flight| unnecessarily displays a fare change issue

Get familiar with the admin actions like Retrieve PNR and find some issues in tripjet.

Reported issues: Bug #20583
Flight| Void and cancel | Incorrectly showing status issue

Gone through the admin side actions of tripjet

Get familiar with admin actions and reported issues in tripjet

reported issues: Bug #20583 Flight| Void and cancel | Incorrectly showing status issue

Test case running (Detail markup)
Reported issues Bug #20889
Flight| Payment method |Continue button loading issue
When a user selects a payment method and is redirected to the payment gateway page, then uses the browser's Back button to return from that page, the "Continue" button stays in a loading state.

Test case running
Applying markup using various criteria, Checked markup on percentage and amount.

Executed test cases for markup using different criteria and applied markup to various content segments to validate functionality and consistency.

Today, I executed test cases and applied markup criteria on the Thathkarahst website. The following conditions were verified:

1)Applied markup based on flight number, both as a percentage and as a fixed amount

2)Markup was tested on Base Fare, Tax, and a combination of both

3)Verified markup application across different trip types: One-way, Round Trip, and Multi-city

4)For Multi-city searches, attempted to apply markup individually to each leg and analyzed fare differences

5)Tested markup behavior across different airlines

Segment-Based Markup:

Learned how markup is applied depending on the number of flight segments.
    Checked conditions like markup per passenger or per booking, and whether fixed markup is enabled or not.
    Applied markup to base fare, taxes, and total price, using both fixed amounts and percentage values.
    Understood how markup calculations change with different segment counts.

Seat, Meal, and Baggage Markup:

Went through how markups are added to meals and baggage services.
    Tested markups in both amount and percentage.
    Set markup for specific seat types and checked how it shows up on the B2C platform and TQR report.

Today, I learned how to apply discounts on the Thathkarahst Website. I tested how discounts work for different types of bookings, such as One-way, Round-trip, and Multicity. I applied both amount-based and percentage-based discounts for these bookings. I also learned how to apply discounts for different people, like Adults, Children, and Infants, in both amounts and percentages. I made sure the discounts were calculated correctly in each case.

Tasks Performed:

Discount Criteria Validation on thathkarahst website based on the following conditions:

Sales Date:

Verified discount application for searches inside the specified sales date range.

Verified discount application outside the sales date range across one-way, multi-city, and round-trip options, in both amount and percentage formats.

Travel Date:

Verified discount application for bookings made within the travel date range for one-way, multi-city, and round-trip, in amount and percentage formats.

Advance Purchase Validity:

Verified discount logic for bookings made within the defined number of advance purchase days.

Flight Number-Based Discounts:

Applied and validated discounts based on specific flight numbers, across same and different airlines.

Data Entry:

Entered details of newly onboarded clients into Excel for record-keeping and tracking.

Issues Observed:

Multi-city Discount Issue:

Discount is not being applied in multi-city bookings when based on flight number.

This is not Reflected in roundtrip and in oneway

validate the behavior of flight number-based discounts across same and different airlines on the Thathkarahst website.

1.Same Airline – Specific Flight Number:

Result: Discount applied successfully.

Reflection: Properly reflected in the B2C portal.

Discount Types Tested:Percentage,Fixed Amount
Discount Application Areas:Base Fare, Tax, Both

Different Airlines – Specific Flight Numbers:

Result: Discount not applied.

Reflection: Not visible on the B2C portal.

Observation: Issue exists when applying discounts across multiple airlines.

Airlines with Segment-Based Journeys (Multi-leg Flights):

Result: Discount not applied.

Observation: Discount fails to reflect when the flight has segments, even if the flight number matches

Issues Identified:

Discount logic is partially functioning:

Works as expected within the same airline

Fails when:

Flight numbers belong to different airlines.

Flights include segments in the journey

Reported issues: -

Flight| markup| Based on Flight Number |Not reflected in B2C Issue

Module: Hotel Section – Maqaam Website

Activities Completed:

Search to Vouchering :

Explored the hotel search to vouchering process

Performed searches based on:

Multiple locations

Varying check-in/check-out dates

Different combinations of number of pax (passengers)

Verified field validations including:

Maximum allowed number of pax per room

Maximum number of rooms that can be booked

Total pax limits per booking

Admin sise

Reviewed admin-side functionalities for hotel bookings.

Identified a bug in the TQR  under Payment Details.

Coupon Code Generation:

Generated a coupon code from the hotel module.

Verified successful application and reflection in the TQR payment details.

4.Reported issues:

bug#21527  
Hotel| Payment details |Cancellation Fee shows Internal Server Error Issue

--

Today, work on the Hotel Section – Maqaam Website focused on applying the hotel markup functionality. Initially, standard markup was applied, including both percentage-based and amount per room/night options. Following that, markup logic was added based on specific criteria. This included applying markup based on the sales date—differentiating between bookings within or outside a specified date range—as well as location-based markup targeting specific countries, cities, and individual properties.

Reported issues:- Bug#21579
Hotel| Guest details shows Internal Server Error Issue

Hi,
1. Apply Pending Markup Criteria

Complete the markup application that was pending from yesterday.

Apply markup rules based on:

Country

City

Property (Hotel)

Verify that the applied markup is correctly reflected in the B2C portal for various combinations of:

Different countries

Different cities

Specific hotels

2. Discount Section

Apply discounts based on the following criteria:

Sales Date

Country

City

Property (Hotel)

Discounts to be applied in both:

Percentage

Amount

Ensure these are applied correctly and validate in the B2C .

3. Study Cancellation Policies

Study cancellation policies across different hotel providers.

Understand:

The differences in cancellation policy structures

Details provided in the hotel booking report by each provider

Agency Management :

Navigated to the Agency Management section.

Created a new agency by entering:

Main Branch details
                             Sales Group information

Created Debit and Credit Users:

Defined credit limits
                           Set initial balances

given 2 different start date and end date

Role Management

Added:

Company
                       Main Branch
                       Agency Type
                       Created a new Role Name
                      Assigned appropriate Permissions to the newly created role.

User Creation

Created a new user:
                  Set Username and Password
                 Assigned the created role
                 Successfully logged in using the new credentials.

B2B Functionality

Performed a B2B Search after logging in with the agency user credentials.

Payment & Wallet Verification
                                           Executed a Top-Up for the agency.
                                           Verified that the amount was successfully deducted from the wallet.
                                           Confirmed balance deduction through the Wallet Report.

1.Tathkarah Website
Created a new agency successfully.
Performed an agency top-up.
Used the topped-up amount to complete ticketing.
Verified deduction of the ticketing amount from the agency’s wallet.

2. Attar Travels
Created a new main branch.
Under the newly created main branch, a new agency was added successfully.
Since the main branch is newly created, all permissions need to be configured, including:
API Management access
Supplier Configuration settings

1.Agency Creation :

Successfully created a new agency in the Attar Travels system.
       Performed an agency wallet top-up to enable transactional capabilities.

2. Ticketing Operations:

Utilized the topped-up wallet amount to complete a ticket booking.
        Verified the deduction of the ticketing amount from the agency wallet post-transaction.

3.Markup and discount:

Added an instant markup and instant discount.
       Validated fare reflection, confirming correct application of markup and discount on the ticket pricing.

4.TQR Admin Verification:

Performed and verified the following admin-level actions in TQR:
               Void and Cancel actions.
               Online void action.
               Confirm Ticket and Queue for Ticket processes for bookings with status B2B Hold Booking.

Hi,

Manual Ticket Configuration

Tested:-
1)Search with all normal conditions:
2)Enabled all airlines, all APIs, all cabins, and all booking classes.
3)Changed conditions to different APIs:
*Tested with Galileo API
*Tested with Amadeus Flight API
*Tested with Sabre API
4)Selected different airlines for testing.
5)Selected different origin and destination combinations.
6)Selected different cabins:
*Economy
*Business Class
*First Class
*Premium Economy

Issues Identified:
      *When adding only one passenger name, the ticket repeatedly displays the same name three times.
      *Manual ticketing is not working in Business Class.

Manual Ticket Configuration:
Completed remaining configuration work left over from yesterday.
Reported identified bugs during the process.

Featured Flight Details:
Reviewed the "Featured Flight Details" section.
Tested with various source and destination combinations.
Tested for both one-way and round-trip journeys.
Set travel dates and verified proper reflection on the B2C platform.
Performed search and ticketing actions using the configured deals.

Featured Hotel Deals:
Reviewed the "Featured Hotel Deals" section.
Tested with multiple check-in and check-out date combinations.
Verified if the details were correctly reflected on the B2C platform.

Tasks Completed:

Bug Retesting:
Retested a set of previously fixed but unverified bugs.
Verified the functionality and closed the bugs after successful testing.

Review Session:
Participated in the scheduled review meeting in the afternoon.
Discussed current progress and received feedback.
spent time revisiting and studying the flight module in detail.
Covered the complete flow from Search → Ticketing to strengthen understanding of the overall process.

Bug Retesting & Update:
Re-tested a previously reported bug.
Added additional clarification and information to the existing bug report.
Posted the updated bug with new findings.
Payment Gateway Setting:
Navigated through the "Payment Gateway Settings" module.
Selected combinations including:
Main Branch
Agency
Property: Flight
Tested with different APIs:
Amadeus
Galileo
Others as applicable

Verified configurations for multiple payment gateways:
KNET
Visa/Mastercard
MADA
Tabby

Applied different service charge types:
Percentage
Fixed

Identified how various API and payment gateway settings are reflected/applied on the B2C portal.
Noted variations in service charge behavior based on selected gateway and API combinations.

Reported issues: -Bug#22232
                Flight| Discount| edit page| does not display previously saved details issue

Studied about how convenience fees are applied across various payment card types and determine whether they are reflected in B2C .

*Studied the application of convenience fees on different payment cards and verified if they are correctly reflected in B2C transactions.
Applied convenience fees across various origins and destinations.
Tested convenience fees with different suppliers.
Applied convenience fees both as fixed amounts and percentages.
Validated the calculation of convenience fees when combined with markups.
Tested convenience fees along with discounts and verified how the calculations are performed and how convenience fees are computed in these scenarios.
Identified issues with some payment gateways, including:
Continuous loading screens.
Retry problems during payment attempts.
The "Continue" button not proceeding in certain cases.

Bug Review Steps:
Reviewed bugs that I reported earlier.
Some of them had recent edits/updates.
Not Reproducible: Marked as "Need More Information" and asked for detailed steps to reproduce.
Description Updates Needed: Edited bug descriptions for clarity and accuracy.

Apply markup according to the following scenarios:

1. Per Booking with Fixed
Apply markup as per the fixed amount.
Confirm markup is correctly applied to the entire booking, not per person.

2. Per Pax with Fixed
Apply markup per individual passenger.
Fixed option is enabled here too.
Validate markup applies correctly per pax.

3.Per Booking – Comparison: Fixed Disabled vs Enabled
Tested behavior with:
Fixed Disabled
Fixed Enabled

Reviewed the process and logic for currency conversion in the system.
Studied the markup and discount structures
Analyzed how different scenarios affect fare calculations.
Explored the Sulthan Sight booking module for the first time.
Studied the full process flow from Search → Booking → Ticketing.

Hotel Search & Ticketing
Performed a normal hotel search.
Proceeded through the ticketing process.

Admin Actions
Reviewed and tested the following admin-level functionalities:
Cancel Booking
Reconfirm Booking
Request Cancellation
Request Refund

Price Verification
Verified how price changes with:
Increased number of nights
Increased number of pax (passengers/guests)

Markup Application

Added markup to a booking.
      Verified its reflection in TQR

Activities Completed:

Hotel Module
Applied markup on hotel bookings and verified its reflection in the B2C flow.
Issue Identified: Passenger details are missing from the normal hotel ticket. Reported for further investigation.

Agency
Created a new agency account.
Booked a hotel using the agency
Performed a wallet top-up for the agency and verified the correct deduction from the wallet balance.

Discounts and Markups:
Applied an instant discount and instant markup on a hotel booking.
Verified that the changes are reflected accurately.

Flight Booking
Set wallet balance to 0.
Booked a flight and verified that the amount was added correctly under Outstanding Price.
Ensured it is reflected accurately.

Hi,
Today focus more on credit balance deposit balance and outstanding balance , study about how outstanding balance be display how to remove outstanding balance by using pending payment in payment management, and the complete process. ticketed using the conform ticketing and Que for ticketing and how it displayed in the wallet, verify when we ticketed a flight each time the the wallet shows the deducted price verify the the amount even if the ticket fails.
And also started studying "behalf" function by selecting different agency,branch and agent.
Reported issues: - Bug 22752
Flight| Agency | Wallet icon didn't display any data issue

1. Maqam Website:
Attempted to book a ticket using the "Behalf Of" option.
After selecting a flight, an error was encountered while using the Behalf Of function.No ticket is generated
Using FTP to investigate the issue.
Reviewed the error logs and identified the cause of the failure during ticketing.

2. TripJet:
Performed booking using the "Behalf Of" function on TripJet.
Faced a few issues during the process, which were identified and reported.
Successfully completed a test using the Behalf Of feature.

3. Verification:
Verified updates and changes in the TQR after using the Behalf Of function.
Confirmed the wallet deduction post-ticketing.
Applied instant discounts and markup in the function
Verified that the payment details were correctly reflected after all adjustments.

Tasks Performed:

Logged in as Credit Agency.
Vouchered tickets with:
1 room
2 rooms
Multi-pax bookings with different adult/child combinations.
Verified TQR (Transaction Query Report).

Admin Actions Verified:
Cancel booking
Cancel booking manually
Refund to customer

Issue Observed:
In Credit Agency login, the calculated cancellation charge is not being displayed in TQR.

Login with Other Roles:
Logged in as Debit and Inhouse user.
Repeated all admin actions mentioned above.

Reports Validation:
Confirmed that all admin actions are correctly reflected in the TQR.

Reported Issues:-Bug #22918
Flight| downloaded ticket shows a 400 Internal Server Error issue

Extras Management (Flights & Hotels Modules):

Add Extras
Enabled display of extras on B2C interface.
Add new names for extras.
Enable/disable extras on a per person basis.

Airlines:
Ability to select individual airlines or select all.

Airports:
Support for selecting different and same airlines combinations.

Travel Direction Options:
Departure
Arrival

TripJet
Added and verified Best Value feature.

Confirmed it is reflected in:
B2C platform
TQR report display

Flight + Hotel

Provided input details:
Source: [e.g., kwi]
Destination: [e.g., DXB]
Travel Date: [e.g., 25th June 2025]
No. of Pax: 2
Cabin Class: Economy

Selected Flight first and then Hotel from the result page.
Proceeded to the Passenger (Pax) details page.
On clicking Continue after submitting pax details:
❌ Issue Observed: Blocker appears.
❗ Error Message: “Something went wrong” popup is displayed.
Bug Status: High Priority – Reported.

Static Package Creation in TripJet
Created a static package by:
Adding Package Style
Selecting Region, Theme, Country, and Category

Entering full package details including:
Number of Days,Airlines,Duration,Price
Verified that the package is visible on the B2C portal
In TripJet, only Enquiry is allowed for static packages.
Emails are triggered to both the Customer and Admin upon enquiry submission.
There is no booking option

Issue ticket in Travelsouq
Issued a round-trip ticket with a base fare
Issued a one-way ticket with base fare with 1 Adult, 2 Children, 1 Infant
Issued a one-way ticket with base fare with 1 Adult, 1 Infant
Issued a one-way ticket with base fare with 1 Adult
In BookSultan
Issued flight tickets
Issued hotel bookings
After-Sales Payment Settings
Selected Supplier: GalileoUAPI
Added Penalties as required
Booked a ticket via My Bookings
Successfully used Void to cancel individual passengers from the same booking
Issue Identified
When attempting to refund each passenger from Admin Panel after voiding:
Refund not processed,A popup is shown instead
System does not allow refund
Reported the issue

PayLater Settings Configuration
Accessed and configured PayLater Settings.
Actions performed:
Selected All and Different Country Sources.
Chose All and Different Source-Destination combinations.
Applied PayLater Charges both in amount and percentage.
Configured settings for multiple journey types: One-Way, Round Trip, and Multi-City.
Verified the PayLater and Down Payment amounts in both B2C users.

4. Fare Summary Validation
Validated full calculation in the Fare Summary section.
Ensured all PayLater and Down Payment amounts are correctly reflected and calculated.

5. Payment Link Creation and Transaction
Payment link successfully created.
Payment was completed via the generated link.
Verified and recorded the transaction

Reviewed Loyalty Points Logic Implementation:
Navigated to the Loyalty Points section in the system.
Selected “Flight” as the property.
Verified parameters: ticket price, loyalty points, and value per point.
Confirmed that the system awards 1 point for every 50 units of ticket price.

Test Execution:
Logged in as a user.
Booked a roundtrip flight from Dubai to Kuwait.
Flight ticket price: 287 units.

According to admin settings:
Only full multiples of 50 are eligible for points.
280 out of 287 is eligible (287 truncated to nearest lower multiple of 50).
280 / 50 = 5.6 ⇒ Truncated to 5 points.
Manually changed the flight travel date to a past date.
Verified that pending points were updated to available points after this change.

Issue Identified:
Expected Points: 5
Actual Points : 6
This indicates a logic error in the loyalty point calculation module — it appears the system is not truncating decimals correctly and is possibly rounding up instead.
Reported the issue

Tested the module with multiple combinations of source, destination, departure dates, and check-in/check-out dates.
Confirmed that the search results for both flights and hotels are loading as expected.

Selection Process:
Successfully selected a flight from the flight results page.
Selected a hotel from the hotel results page.
Chose 1 room and entered passenger details.
Clicked on Continue to proceed.

Ticketing Flow:
Completed the booking and reached the ticketing phase.
Verified admin status updates including:
Ticketed
Ticket Pending
Partially Ticketed

Confirmed statuses are reflecting accurately in the admin panel.
Additional Functionalities Tested:
Applied Coupon Code and verified successful discount application.
Convenience Fee was correctly calculated and added to the total fare.

Convenience Fee IN F+H:
Tested the application of convenience fee in both amount and percentage formats.
Used multiple combinations of:
Varying PAX counts
Different numbers of hotel rooms

Observation:
The convenience fee was applied to all bookings, regardless of the configuration set in the Admin settings.
Expected Behavior:The convenience fee should apply only when the source, destination, and hotel city match the values configured in Admin settings.
Bug is reported

Best Value Application in F+H:
Applied the Best Value setting in the F+H.
Verified that it is correctly reflected in the TQR.

whats App Settings & PG Settings Verification:
Verified that these configurations are also reflected in the TQR.

Flight Booking Module:

Tested multi-passenger bookings using one-way, round-trip, and multi-city options.
Verified all price details are correctly applied and accurately reflected in the TQR
Applied and validated markup, discounts, and coupon codes; confirmed all changes are correctly reflected in the TQR.
Conducted tests in Arabic language interface to ensure consistent behavior and accurate reflections.
Logged in as an agency user and repeated all above tests to confirm functionality from the agency perspective.

Hotel Module:

Booked voucher tickets with multiple passengers and verified the details are properly reflected in the TQR.
Applied markup and discounts and confirmed these are correctly shown in the TQR.
Also tested the hotel module functionality in Arabic.

Today, I attempted to create a fixed package in Maqam. The process included:
Setting up all inventory suppliers.
Completing configurations for:
Transport
Hotel
Activity
Transfers
Package

Verifying the package visibility on B2C.
However, the package was not reflected on the B2C platform. This may have been due to an error on my part during the configuration process.
I will recheck all steps tomorrow and correct any misconfigurations if found.

Created and successfully displayed the Fixed Package in B2C today.
Corrected all date-related issues that existed yesterday.
Added more information to the package as required.
Properly configured all modules:
Transport
Hotel
Activity
Transfers
Package
Reported some bugs found during the process.

today i attended review session , and affter the session there is a task to study about the pnr
studided about what is pnr, how it is cerated
when it is generated
how we cance;l airline opnr and gds opnr abut split pnr
about admin actions like cancelled booking
cancel booking manually
handler
void and cancel and online void report it as an eod

Today I studied about online void action,
about split PNR – how it works, in which providers it is available, and what changes occur after the online void process.
Retrieve PNR
Retrieve ticketing
Confirm ticketing and queue for ticketing

Today, I studied the admin actions involved in the ticketing process, including confirming ticketing, queuing for ticketing, and syncing the PNR.

Today, I studied the following topics:

CAXML Out

Travel Fusion

Sync PNR

Confirm Ticketing

Queue for Ticketing

Today studied about
Reissue
manual ticket configuration

reported issues:
Bug #24104
Bug #24097
Bug #24021

Learned about various scenarios related to ticket reissue and identified/reported some bugs.

Studied the agency concept, including different types of agencies.

Gained understanding of wallet deductions and the agency top-up process.

Agency Concept – Workflow Overview
Studied the overall functioning of the Inhouse Agency model.
Understood the "On Behalf Of" functionality and how it impacts operations.
Key Modules Covered:
Generate Direct Payment
Agency Topup
Agency Topup Approval
Pending Payment
Wallet Deduction

Operational Flow Understood:
From normal search → to ticketing → including on-hold scenarios.
Ticketing , especially with agency involvement.

Today, I continued with the study and practical exercises related to Agency Management, specifically focusing on ticketing flows and related operations.
Logged in as a debit agent.
Searched and reviewed issued tickets.
Verified TQR, booking details, itinerary, and payment

Manual Ticketing (Using Behalf):
Performed manual ticketing through the "Behalf" option.
Ticketing Operations & Admin Actions:
Issued a test ticket and logged in as an admin.
Performed Void, Cancel, and related admin actions successfully.
Processed a refund to a customer using the wallet system.

Wallet & Balance Check:
Simulated a transaction with an empty wallet
Verified system response and checked outstanding balance handling.

Review Session:
Attended a review session in the afternoon

Today I learned about each field in the main branch, including:
City code
Currency code
Country

Studied passport optional settings.
Covered agency management, including:
Sales group
Agency name
Type
Also explored different fields in the agency management report.

Today, I learned about the Agency Concept, including:
Managing roles
Setting agency permissions
Payment gateway management
Understanding different types of travel agents:
Credit agencies
Debit agencies

Today, I studied about the key aspects of agency management. The areas covered included:
Understanding the Branch Unit structure
Studying the Agency Top-Up process
Reviewing the Agency Top-Up Approval
Examining Pending Payments
Studied about the Wallet Deduction mechanism

Today, I learned about the following concepts:

Agency concept

Pending payment

Wallet deduction

Outstanding balance

Outstanding balance deduction

Today, I learned about the concept of agency, gaining a better understanding of its principles and applications. In the evening, I attended a review session.

Today's Summary:
Studied the Agency Concept

STUDIED
Agency Top-up
Agency Top-up Approval
Pending Payments
Wallet Deduction

Studied about the Currency Conversion

Studied the markup section, including basic concepts and applications.
Worked on a normal markup scenario, applying markup:
In fixed amount
In percentage

Attended a review session

Today, I was assigned to work on the documentation of the Fixed Package. As part of this task, I reviewed the Fixed Package configuration on the admin side and studied each field in detail to gain a thorough understanding of its functionality and purpose.

Create test cases for fixed package