Reservations : Reservation recap : Modifying the Recap dialog
 
Modifying the Recap dialog
 
The Recap dialog layout can be custom formatted. To do this, locate the Recap dialog code in the <defaults> section of the SysManager > Preferences > Miscellaneous > Global Salespoint .INI tab (see example below). Tags can be added or removed specific to your operation.
1. Recap Header. This is a single line of text that can be customized for your operation.
RecapTextBegin= Enter any system wide text you want right here such as instructions to your operators... <cr>____________________________________________________________
 
2. Recap body – Reservation Header info. This contains the Reservation Header info. By default, most fields from the header are included here; if some are not needed, they can be removed from the Recap dialog to condense the amount of text on the dialog.
ResDescRecap=Guest: <first_name> <last_name><cr>Status: <sale_status><cr>Reservation#: <reserv_no><cr>Confirmation#: <user_resno><cr>Arrival Date: <start_date><cr>Pickup Location: <pickup_loc><cr>Base Lodge: <base_lodge><cr>Accommodations: <accommodat><cr>Print Tickets: <Print_due><cr>Final Payment Due: <final_due><cr>Tracking#: <tracking1., <tracking2>
 
Sample section: ResDescRecap=Guest: <first_name> <last_name> --
This section is the top of the Reservation Header info on the Recap dialog and displays the text Guest: followed by the first and last name of the primary guest in the reservation. Because this section starts with the ResDescRecap tag, the system automatically knows to pull all info in this section from the Reservation Header that corresponds to fields in the Resrvatn data table.
3. Recap body – item/transaction info. This contains the transaction info from the sale.
ItemDescRecap=________________________________________________________<cr><ret_stat><cr>Qty: <qty> Item: <items->descrip> <ifspecial>Special: <specials->descrip> Discount Amount: <tr_save->disc_amt></ifspecial> Cost: $<ext>each<cr><cr><ifmods>Activities:<cr></ifmods><ifmods><formods>Qty: <qty> <items->descrip> <ifspecial>Special: <specials->descrip> Discount Amount: <tr_save->disc_amt></ifspecial> Cost: $<ext>each<cr></formods></ifmods><cr><cr>Start Date: <date><cr><cr><ifguest><forguests>Guest: <guests->first_name> <guests->last_name><cr></forguests></ifguest><cr><ifpod><forbooks>Resource: <b_sched->podname> Booking Date/Time: <b_sched->start_time><cr></forbooks></ifpod><ifprivate><forbooks>Instructor: <b_sched->instrname> Lesson Date/Time: <b_sched->start_time><cr></forbooks></ifprivate><cr><iftee><fortee>Tee-time: <res_schd->start_time></fortee></iftee><cr>Meeting Location: <meet_loc><cr><iffinalized>Printed On: <tr_save->date_time></iffinalized>
 
 
Sample section: <ifguest><forguests>Guest: <guests->first_name> <guests->last_name><cr></forguests></ifguest>
This is a conditional statement in the above section. Basically, it says, if a guest name is attached to the product, then display the first name and the last name in the Recap.
 
Note: Conditional statements start with open tag (e.g., <ifguest> ) and end with a close tag (e.g., </ifguest>).
 
The <cr> that is scattered throughout the recap is for carriage returns. These can be added or removed as needed.
4. Recap body – sales info. This contains the payment info from the sale.
ResDescRecap2=________________________________________________________<cr>Payment Summary<cr><cr>Reservation Grand Total: <res_total><cr>Total Payments Made: <amt_paid><cr>Balance Due: <bal_due><cr>Forfeited Amount: <fft_total><cr>Refunded Amount: <ref_total><cr>____________________________________________________________<cr>Payment Detail<cr><cr><forpmts>Payment Date: <pmt->Date_time><cr>Amount: <pmt->amount><cr>Payment Type: <pmt->Pmt_type><cr><iscard>Card Number: <pmt->Card_no></iscard><cr>At Salespoint: <pmt->Salespoint><cr>By Operator: <pmt->Operator><cr><cr></forpmts>
 
5. Recap footer. This is a single line of text that can be customized for your operation.
RecapTextEnd=_________________________________________________________<cr>Enter more system wide text here, such as a cancellation policy or anything else your operators communicate to your guests...