kanimozhi
/
communityhallv22
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
26 Commits
1 Branch
0 Tags
244 MiB
Tree: 1d516f8e10
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1d516f8e10'
${ noResults }
communityhallv22/src/main/resources/templates/user/viewhistory.html

3569 lines
201 KiB
Raw Normal View History

first
2 years ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community Hall new changes code updation
2 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
first
2 years ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Enhancement added and Bugs fixed
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Sir p t hall restriction and community hall center list has been changed
7 months ago
changed bookingid to referenceid in acknowledgement page
11 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
changed bookingid to referenceid in acknowledgement page
11 months ago
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
​
​
​
changed bookingid to referenceid in acknowledgement page
11 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
changed bookingid to referenceid in acknowledgement page
11 months ago
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
changed bookingid to referenceid in acknowledgement page
11 months ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
changed bookingid to referenceid in acknowledgement page
11 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
changed bookingid to referenceid in acknowledgement page
11 months ago
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
first
2 years ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community Hall new changes code updation
2 months ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community Hall new changes code updation
2 months ago
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
first
2 years ago
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
changed bookingid to referenceid in acknowledgement page
11 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
​
changed bookingid to referenceid in acknowledgement page
11 months ago
Sir p t hall restriction and community hall center list has been changed
7 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Counter Report added for Admin login
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Counter Report added for Admin login
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community Hall new changes code updation
2 months ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community Hall new changes code updation
2 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community Hall new changes code updation
2 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community Hall new changes code updation
2 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Community Hall new changes code updation
2 months ago
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Community Hall new changes code updation
2 months ago
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Community Hall new changes code updation
2 months ago
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Community Hall new changes code updation
2 months ago
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Community Hall new changes code updation
2 months ago
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
Hall creation and Gcc Blocking(New) concept implemented in the Admin, HQ and officer login
3 months ago
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
Six month old transactions option created for HQ login and mail integration implemented.
3 months ago
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
CareTaker, Officer and Counter Login creation page added in HQ
4 months ago
​
​
Community Hall new changes code updation
2 months ago
CareTaker, Officer and Counter Login creation page added in HQ
4 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Sir p t hall restriction and community hall center list has been changed
7 months ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community Hall new changes code updation
2 months ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
Community Hall new changes code updation
2 months ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
CareTaker, Officer and Counter Login creation page added in HQ
4 months ago
Community Hall new changes code updation
2 months ago
​
CareTaker, Officer and Counter Login creation page added in HQ
4 months ago
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
CareTaker, Officer and Counter Login creation page added in HQ
4 months ago
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community Hall new changes code updation
2 months ago
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
CareTaker, Officer and Counter Login creation page added in HQ
4 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
Community Hall new changes code updation
2 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
Community Hall new changes code updation
2 months ago
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
first
2 years ago
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
first
2 years ago
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Community hall updated code with the following changes 1. Admin login --> In Transaction response report temp transactions will be visible 2. Settlement Pending List --> If any error/issue occurs during settlement it will be moved to Refund Failed List 3. Admin Reports --> i) Users -> User Id added in ascending order ii) Users Booking List --> User Id added in ascending order iii) Hall Booking List --> Hall Id added in total bookings in descending order 4. Cancel Booking Enabled for booking status Waiting for NOC and Waiting for NOC Approval.
1 year ago
​
Community Hall new changes code updation
2 months ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
first
2 years ago
Scheduler refund amount code disabled and right click disabled and coniditon added in 3rd step of hall booking form
1 year ago
​
​
first
2 years ago
​
​
  1. <!DOCTYPE html>
  2. <html lang="en" xmlns:th="http://www.w3.org/1999/xhtml">
  4. <head th:replace="~{fragments/head :: head}">
  5. </head>
  6. <!--datatables-->
  7. <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/1.13.4/css/jquery.dataTables.min.css">
  8. <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/buttons/2.4.1/css/buttons.dataTables.min.css">
  9. <style>
  10. .card-body table {
  11. width: 100%;
  12. padding: 100px;
  13. }
  15. .card-body th,
  16. td {
  17. padding: 8px;
  18. text-align: left;
  19. }
  21. .amount-cell {
  22. text-align: right;
  23. padding-right: 1rem;
  24. /* Adjust padding as needed */
  25. }
  27. .ui-datepicker-container {
  28. width: 100%;
  29. }
  31. .fixedcontainer {
  32. width: 250%;
  33. margin: 40px 0;
  34. display: none
  35. }
  37. .disabled {
  38. cursor: not-allowed;
  39. opacity: 1;
  40. }
  42. /* Move pointer-events:none to the inner anchor so the <td> can still receive
  43. mouse events (needed for title-attribute tooltips and event delegation) */
  44. .disabled a,
  45. .disabled .ui-state-default {
  46. pointer-events: none;
  47. cursor: not-allowed;
  48. }
  50. /* ── Custom datepicker tooltip (works even when .disabled has pointer-events:none) ── */
  51. #dp-tooltip {
  52. position: fixed;
  53. z-index: 9999;
  54. background: rgba(30, 30, 30, 0.92);
  55. color: #fff;
  56. padding: 5px 11px;
  57. border-radius: 6px;
  58. font-size: 12px;
  59. font-weight: 600;
  60. pointer-events: none;
  61. white-space: nowrap;
  62. box-shadow: 0 2px 8px rgba(0, 0, 0, 0.3);
  63. display: none;
  64. transition: opacity 0.15s;
  65. }
  67. .ui-widget {
  68. width: 40%
  69. }
  71. .ui-datepicker {
  72. padding: 3px;
  73. border: 1px solid #ccc;
  74. border-radius: 5px;
  75. background-color: white;
  76. left: 29.1418px;
  77. }
  79. .ui-datepicker-header {
  80. background-color: #f0f0f0;
  81. border: none;
  82. border-radius: 5px 5px 0 0;
  83. }
  85. .ui-datepicker-title {
  86. font-size: 1.2em;
  87. margin: 0;
  88. padding: 10px;
  89. text-align: center;
  90. }
  92. .ui-datepicker-calendar {
  93. margin: 0;
  94. padding: 0;
  95. font-weight: bold;
  96. }
  98. .ui-datepicker-calendar th,
  99. .ui-datepicker-calendar td {
  100. padding: 5px;
  101. text-align: center;
  102. }
  104. .ui-datepicker-calendar .ui-state-default {
  105. cursor: pointer;
  106. width: 100%;
  107. height: 100%;
  108. display: flex;
  109. justify-content: center;
  110. align-items: center;
  111. }
  113. .ui-datepicker-week-end {
  114. color: black;
  115. font-weight: bold;
  116. }
  118. .ui-datepicker-calendar th span {
  119. color: black;
  120. font-weight: bold;
  121. }
  123. .highlight-blue .ui-state-default {
  124. background: blue !important;
  125. color: #FFF !important;
  126. }
  128. .highlight-greens .ui-state-default {
  129. background: green !important;
  130. color: #FFF !important;
  131. }
  133. .highlight-yellow .ui-state-default {
  134. background: yellow !important;
  135. color: #000 !important;
  136. }
  138. .highlight-violet .ui-state-default {
  139. background: #a93da9 !important;
  140. color: #000 !important;
  141. }
  143. .highlight-pink .ui-state-default {
  144. background: red !important;
  145. color: #000 !important;
  146. }
  148. .form-control[readonly] {
  149. background-color: white;
  150. }
  152. .modal {
  153. overflow-y: auto;
  154. }
  156. .stepper-wrapper {
  157. display: flex;
  158. justify-content: space-between;
  159. margin-bottom: 20px;
  160. position: relative;
  161. }
  163. .stepper-item {
  164. display: flex;
  165. flex-direction: column;
  166. position: relative;
  167. width: 100%;
  168. z-index: 1;
  169. }
  171. .stepper-item::before {
  172. content: '';
  173. position: absolute;
  174. top: 15px;
  175. left: 50%;
  176. height: 4px;
  177. background-color: #dcdcdc;
  178. /* Default grey line */
  179. z-index: -1;
  180. }
  182. .stepper-item:first-child::before {
  183. left: 50%;
  184. width: 0;
  185. }
  187. .stepper-item:last-child::before {
  188. content: none;
  189. }
  191. .stepper-item.completed:not(:last-child)::after {
  192. content: '';
  193. position: absolute;
  194. top: 15px;
  195. left: 50%;
  196. width: calc(100% - 30px);
  197. height: 4px;
  198. background-color: #28a745;
  199. z-index: -1;
  200. transform: translateX(-50%);
  201. }
  203. .step-counter {
  204. width: 30px;
  205. height: 30px;
  206. border-radius: 50%;
  207. background-color: #dcdcdc;
  208. display: flex;
  209. justify-content: center;
  210. align-items: center;
  211. font-weight: bold;
  212. color: white;
  213. }
  215. .step-name {
  216. margin-top: 10px;
  217. font-size: 11px;
  218. }
  220. .stepper-item.completed .step-counter {
  221. background-color: #28a745;
  222. }
  224. .stepper-item.completed .step-name {
  225. font-weight: bold;
  226. }
  228. .tracking-container {
  229. padding: 10px;
  230. background: #f9f9f9;
  231. border-radius: 8px;
  232. overflow: hidden;
  233. max-height: 500px;
  234. }
  236. .tracking-steps {
  237. list-style: none;
  238. padding: 0;
  239. margin: 0;
  240. position: relative;
  241. }
  243. .tracking-steps::before {
  244. content: '';
  245. position: absolute;
  246. top: 0;
  247. left: 8px;
  248. width: 4px;
  249. height: 100%;
  250. background: yellowgreen;
  251. z-index: 0;
  252. }
  254. .tracking-step {
  255. display: flex;
  256. align-items: flex-start;
  257. margin-bottom: 20px;
  258. position: relative;
  259. padding-left: 40px;
  260. text-align: center;
  261. border-bottom: 1px solid #ddd;
  262. transition: background-color 0.3s ease-in-out;
  263. background-color: #fff;
  264. /* White background for steps */
  265. border-radius: 5px;
  266. /* Optional rounded corners */
  267. box-shadow: 0 1px 3px rgba(0, 0, 0, 0.1);
  268. }
  270. /* Line adjustments between steps */
  271. .tracking-step::before {
  272. width: 100%;
  273. height: 5px;
  274. background: yellowgreen;
  275. /* Line color */
  276. position: absolute;
  277. top: 10px;
  278. /* Adjust position to connect icons */
  279. left: 8px;
  280. /* Aligns with step icons */
  281. margin: 0;
  282. }
  284. .tracking-step:first-child::before {
  285. background: none;
  286. /* No line before the first step */
  287. }
  289. /* Step icon styling */
  290. .step-icon {
  291. flex-shrink: 0;
  292. font-size: 1.5em;
  293. margin-right: 15px;
  294. position: absolute;
  295. left: 0;
  296. top: 0;
  297. width: 20px;
  298. height: 20px;
  299. border-radius: 50%;
  300. display: flex;
  301. justify-content: center;
  302. align-items: center;
  303. background: #ccc;
  304. /* Default icon background */
  305. border: 4px solid #ccc;
  306. /* Default border */
  307. color: #eee;
  308. font-size: 14px;
  309. line-height: 20px;
  310. z-index: 1;
  311. font-family: "Ionicons";
  312. /* Icon font */
  313. }
  315. /* Completed step icon and line color */
  316. .tracking-step.completed .step-icon {
  317. background: #56B500;
  318. /* Green for completed */
  319. border-color: #56B500;
  320. color: #fff;
  321. }
  323. .tracking-step.completed::before {
  324. background: #56B500;
  325. /* Green line for completed steps */
  326. }
  328. .tracking-step.completed {
  329. background-color: #e6ffe6;
  330. }
  332. /* Waiting step icon and line color */
  333. .tracking-step.waiting .step-icon {
  334. background: #ffeb3b;
  335. /* Yellow for waiting */
  336. border-color: #ffeb3b;
  337. }
  339. .tracking-step.waiting {
  340. background-color: #fff3cd;
  341. }
  343. /* Initiated step icon and line color */
  344. .tracking-step.initiated .step-icon {
  345. background: #03a9f4;
  346. /* Blue for initiated */
  347. border-color: #03a9f4;
  348. }
  350. .tracking-step.initiated {
  351. background-color: #cce5ff;
  352. }
  354. /* Pending step icon and line color */
  355. .tracking-step.pending .step-icon {
  356. background: #9e9e9e;
  357. /* Grey for pending */
  358. border-color: #9e9e9e;
  359. }
  361. /* Cancelled step icon and line color */
  362. .tracking-step.cancelled .step-icon {
  363. background: #dc3545 !important;
  364. /* Red for cancelled */
  365. border-color: #dc3545 !important;
  366. color: #fff !important;
  367. }
  369. .tracking-step.cancelled::before {
  370. background: #dc3545 !important;
  371. /* Red line for cancelled steps */
  372. }
  374. .tracking-step.cancelled {
  375. background-color: #fdecea;
  376. /* Light red background for cancelled steps */
  377. }
  379. /* Rejected step icon and line color */
  380. .tracking-step.rejected .step-icon {
  381. background: #ff0000;
  382. /* Dark red for rejected */
  383. border-color: #ff0000;
  384. color: #fff;
  385. }
  387. .tracking-step.rejected {
  388. background-color: #ffe6e6;
  389. }
  391. .tracking-step.rejected::before {
  392. background: #ff0000;
  393. /* Dark red line for rejected steps */
  394. }
  396. /* GCC Blocked step icon and line color */
  397. .tracking-step.gcc-blocked .step-icon {
  398. background: #ff6600;
  399. /* Orange for GCC blocked */
  400. border-color: #ff6600;
  401. color: #fff;
  402. }
  404. .tracking-step.gcc-blocked {
  405. background-color: #ffe0cc;
  406. }
  408. .tracking-step.gcc-blocked::before {
  409. background: #ff6600;
  410. /* Orange line for GCC blocked steps */
  411. }
  413. /* Step content styling */
  414. .step-content {
  415. padding: 2px 15px;
  416. background: #fff;
  417. border: 1px solid #ddd;
  418. border-radius: 5px;
  419. width: 100%;
  420. flex-grow: 1;
  421. box-shadow: 0 1px 3px rgba(0, 0, 0, 0.1);
  422. }
  424. .step-content h5 {
  425. margin: 0 0 5px;
  426. font-size: 16px;
  427. font-weight: bold;
  428. }
  430. .step-date {
  431. color: #666;
  432. font-size: 14px;
  433. }
  435. /* Icon color customization */
  436. .fas,
  437. .fa-solid {
  438. font-weight: 900;
  439. color: white;
  440. }
  442. #transactionmodel {
  443. max-width: 90%;
  444. /* Make modal wider */
  445. }
  447. .table-responsive {
  448. max-height: 400px;
  449. /* Adjust the table's maximum height */
  450. overflow-y: auto;
  451. /* Enable vertical scrolling if needed */
  452. }
  454. body {
  455. font-family: Arial, sans-serif;
  456. }
  458. .chat-icon {
  459. position: fixed;
  460. bottom: 20px;
  461. right: 20px;
  462. width: 60px;
  463. height: 60px;
  464. background-color: #007bff;
  465. border-radius: 50%;
  466. cursor: pointer;
  467. display: flex;
  468. align-items: center;
  469. justify-content: center;
  470. }
  472. .chat-icon img {
  473. width: 30px;
  474. height: 30px;
  475. }
  477. .chat-notification {
  478. position: absolute;
  479. top: -10px;
  480. right: -10px;
  481. background-color: red;
  482. color: white;
  483. border-radius: 50%;
  484. padding: 5px;
  485. font-size: 12px;
  486. }
  488. .chat-box {
  489. position: fixed;
  490. bottom: 90px;
  491. right: 20px;
  492. width: 300px;
  493. height: 400px;
  494. background-color: white;
  495. border: 1px solid #ccc;
  496. display: none;
  497. flex-direction: column;
  498. box-shadow: 0px 0px 10px rgba(0, 0, 0, 0.1);
  499. }
  501. .chat-header {
  502. background-color: #007bff;
  503. color: white;
  504. padding: 10px;
  505. display: flex;
  506. justify-content: space-between;
  507. align-items: center;
  508. }
  510. .chat-body {
  511. flex-grow: 1;
  512. padding: 10px;
  513. overflow-y: scroll;
  514. border-top: 1px solid #ccc;
  515. border-bottom: 1px solid #ccc;
  516. }
  518. .chat-footer {
  519. display: flex;
  520. padding: 10px;
  521. }
  523. .chat-footer input {
  524. flex-grow: 1;
  525. padding: 5px;
  526. margin-right: 10px;
  527. }
  529. .chat-footer button {
  530. background-color: #007bff;
  531. color: white;
  532. border: none;
  533. padding: 5px 10px;
  534. cursor: pointer;
  535. }
  537. .otp-input-box {
  538. display: flex;
  539. justify-content: center;
  540. gap: 10px;
  541. margin: 20px 0;
  542. }
  544. .otp-input-box .otp-input {
  545. width: 40px;
  546. height: 40px;
  547. text-align: center;
  548. font-size: 16px;
  549. border: 1px solid #ccc;
  550. border-radius: 5px;
  551. }
  553. td.highlight-blue.ui-state-disabled {
  554. opacity: 1 !important;
  555. }
  557. td.highlight-blue.ui-state-disabled .ui-state-default,
  558. td.highlight-blue.ui-state-disabled a,
  559. td.highlight-blue.ui-state-disabled span {
  560. background: blue !important;
  561. color: #fff !important;
  562. cursor: not-allowed !important;
  563. pointer-events: auto !important;
  564. }
  566. td.highlight-violet.ui-state-disabled {
  567. opacity: 1 !important;
  568. }
  570. td.highlight-yellow.ui-state-disabled {
  571. opacity: 1 !important;
  572. }
  574. td.highlight-pink.ui-state-disabled {
  575. opacity: 1 !important;
  576. }
  577. </style>
  579. <body>
  580. <!-- Pre-loader start -->
  581. <div class="theme-loader">
  582. <div class="ball-scale">
  583. <div class='contain'>
  584. <div class="ring">
  585. <div class="frame"></div>
  586. </div>
  587. <div class="ring">
  588. <div class="frame"></div>
  589. </div>
  590. <div class="ring">
  591. <div class="frame"></div>
  592. </div>
  593. <div class="ring">
  594. <div class="frame"></div>
  595. </div>
  596. <div class="ring">
  597. <div class="frame"></div>
  598. </div>
  599. <div class="ring">
  600. <div class="frame"></div>
  601. </div>
  602. <div class="ring">
  603. <div class="frame"></div>
  604. </div>
  605. <div class="ring">
  606. <div class="frame"></div>
  607. </div>
  608. <div class="ring">
  609. <div class="frame"></div>
  610. </div>
  611. <div class="ring">
  612. <div class="frame"></div>
  613. </div>
  614. </div>
  615. </div>
  616. </div>
  617. <!-- Pre-loader end -->
  619. <div id="pcoded" class="pcoded">
  620. <div class="pcoded-container">
  621. <!-- Menu header start -->
  622. <nav th:replace="~{fragments/nav-user :: nav}"></nav>
  624. <!-- Menu header end -->
  625. <div class="pcoded-main-container">
  626. <nav th:replace="~{fragments/nav-usermenu :: nav}"></nav>
  627. <div class="pcoded-wrapper">
  628. <div class="pcoded-content">
  629. <div class="pcoded-inner-content">
  631. <!-- Main-body start -->
  632. <div class="main-body" style="background-color: white">
  633. <div class="page-wrapper" style="padding: 0;">
  634. <!-- Page-header start -->
  635. <div class="page-header m-t-50">
  637. </div>
  638. <div id="futureEventsContainer" class="page-body" style="display: none;"></div>
  639. <div class="card">
  640. <div class="card-header">
  641. <h5>Hall Booking Details</h5>
  642. <button type="button" class="btn btn-primary btn-square-md"
  643. th:if="${userBookingspast.size() > 0}"
  644. th:onclick="'transactionHistory(' + ${userBookingspast[0].users_user_id} + ')'">
  645. Transaction History
  646. </button>
  647. </div>
  649. <div class="card-block">
  650. <div class="table-responsive">
  651. <table
  652. class="table table-bordered table-striped table-vcenter js-dataTable-responsive"
  653. id="detailstable" style="width: 100%">
  654. <thead class="thead-light">
  655. <tr>
  656. <th class="text-center no-sort" width="10%">S.No</th>
  657. <th>Booking Id</th>
  658. <th>Booking date</th>
  659. <th>Hall Name</th>
  660. <th>Starting Date</th>
  661. <th>Ending Date</th>
  662. <th>Starting Period</th>
  663. <th>Ending Period</th>
  664. <th>Reason for booking</th>
  665. <th>Booking Status</th>
  666. <th>Payment Status</th>
  667. <th>Event Status</th>
  668. <th class="text-center no-sort" width="10%">Action</th>
  669. <th>View</th>
  670. </tr>
  671. </thead>
  672. <tbody>
  673. <tr th:each="booking, i : ${userBookingspast}"
  674. class="${userBookingspast}">
  675. <td th:text="${i.count}"></td>
  676. <td th:text="${booking.booking_id}"></td>
  677. <td th:text="${booking.booking_date}"></td>
  678. <td th:text="${booking.hall_name}"></td>
  679. <td th:text="${booking.start_date}"></td>
  680. <td th:text="${booking.end_date}"></td>
  681. <td
  682. th:text="${booking.starting_slot == 1 ? 'morning' : (booking.starting_slot == 2 ? 'evening' : '')}">
  683. </td>
  684. <td
  685. th:text="${booking.ending_slot == 1 ? 'morning' : (booking.ending_slot == 2 ? 'evening' : '')}">
  686. </td>
  687. <td th:text="${booking.reason}"></td>
  688. <td
  689. th:text="${#strings.replace(booking.booking_status, '_', ' ')}">
  690. </td>
  691. <td
  692. th:text="${booking.payment_status != null ? booking.payment_status : 'NA'}">
  693. </td>
  694. <td>
  695. <span th:if="${booking.booking_status == 'APPROVED'}">
  696. <span th:switch="${booking.event_category}">
  697. <span th:case="'Current'">Current Event</span>
  698. <span th:case="'Past'">Completed Event</span>
  699. <span th:case="'Future'">Upcoming Event</span>
  700. <span th:case="'Reschedule'">Upcoming
  701. Event</span>
  702. <span th:case="'noaction'">Govt Event</span>
  703. </span>
  704. </span>
  705. <span th:if="${booking.booking_status == 'COMPLETED'}">
  706. <span>Refund Completed Event</span>
  707. </span>
  708. <span th:if="${booking.booking_status == 'CANCELED'}">
  709. <span>User Canceled Event</span>
  710. </span>
  711. <span th:if="${booking.booking_status == 'REJECTED'}">
  712. <span>GCC Rejected Event</span>
  713. </span>
  714. <span
  715. th:if="${booking.booking_status == 'GCC_BLOCKED'}">
  716. <span>GCC Blocked Event</span>
  717. </span>
  718. <span
  719. th:if="${booking.booking_status == 'WAITING_FOR_NOC'}">
  720. <span>Waiting For NOC Document</span>
  721. </span>
  722. <span
  723. th:if="${booking.booking_status == 'WAITING_FOR_NOC_APPROVAL'}">
  724. <span>Waiting For Admin Approval</span>
  725. </span>
  726. </td>
  727. <td th:switch="${booking.event_category}">
  729. <p th:case="'Future'">
  730. <a class="view-button"
  731. th:if="${booking.booking_status == 'APPROVED'}">
  732. <span class="badge bg-danger"
  733. style="cursor: pointer;"
  734. th:onclick="cancelBooking([[${booking.booking_id}]], [[${booking.mobile_no}]], [[${booking.booking_type}]])">Cancel
  735. Booking</span>
  736. </a>
  737. </p>
  738. <p th:case="'waitingfornoc'">
  739. <a class="view-button"
  740. th:if="${booking.booking_status == 'WAITING_FOR_NOC'}">
  741. <span class="badge bg-danger"
  742. style="cursor: pointer;"
  743. data-bs-toggle="modal"
  744. data-bs-target="#uploadNocModal"
  745. th:attr="data-booking-id=${booking.booking_id}">Upload
  746. NOC</span>
  747. </a>
  749. <a class="view-button"
  750. th:if="${booking.booking_status == 'WAITING_FOR_NOC'}">
  751. <span class="badge bg-danger"
  752. style="cursor: pointer;"
  753. th:onclick="cancelBooking([[${booking.booking_id}]], [[${booking.mobile_no}]], [[${booking.booking_type}]])">Cancel
  754. Booking</span>
  755. </a>
  757. <a class="reschedule-button"
  758. th:if="${booking.booking_status == 'WAITING_FOR_NOC' and booking.schedule_count < 1}">
  759. <span class="badge bg-danger"
  760. style="cursor: pointer;"
  761. th:onclick="openRescheduleModal([[${booking.booking_id}]], [[${booking.start_date}]], [[${booking.end_date}]],[[${booking.no_of_days}]],
  762. [[${booking.hall_details_hall_id}]],[[${booking.starting_slot}]],[[${booking.ending_slot}]],[[${booking.reason}]])">Reschedule
  763. Booking</span>
  764. </a>
  765. </p>
  767. <p th:case="'waitingfornocapproval'">
  768. <a class="view-button"
  769. th:if="${booking.booking_status == 'WAITING_FOR_NOC_APPROVAL'}">
  770. <span class="badge bg-danger"
  771. style="cursor: pointer;"
  772. th:onclick="cancelBooking([[${booking.booking_id}]], [[${booking.mobile_no}]], [[${booking.booking_type}]])">Cancel
  773. Booking</span>
  774. </a>
  775. <a class="reschedule-button"
  776. th:if="${booking.booking_status == 'WAITING_FOR_NOC_APPROVAL' and booking.schedule_count < 1}">
  777. <span class="badge bg-danger"
  778. style="cursor: pointer;"
  779. th:onclick="openRescheduleModal([[${booking.booking_id}]], [[${booking.start_date}]], [[${booking.end_date}]],[[${booking.no_of_days}]],
  780. [[${booking.hall_details_hall_id}]],[[${booking.starting_slot}]],[[${booking.ending_slot}]],[[${booking.reason}]])">Reschedule
  781. Booking</span>
  782. </a>
  783. </p>
  784. <!--<p th:case="'noaction'">
  785. <a class="view-button">
  786. <span>&#45;&#45;No Action&#45;&#45;</span>
  787. </a>
  788. </p>-->
  790. <p th:case="'noaction'">
  791. <a class="view-button">
  792. <a class="view-button"
  793. th:if="${booking.booking_status == 'APPROVED'}">
  794. <span class="badge bg-danger"
  795. style="cursor: pointer;"
  796. th:onclick="cancelBooking([[${booking.booking_id}]], [[${booking.mobile_no}]], [[${booking.booking_type}]])">Cancel
  797. Booking</span>
  798. </a>
  799. </a>
  800. </p>
  801. <p th:case="'noaction'">
  802. <a class="view-button">
  803. <span>--No Action--</span>
  804. </a>
  805. </p>
  806. <p th:case="'Reschedule'">
  807. <a class="view-button"
  808. th:if="${booking.booking_status == 'APPROVED'}">
  809. <span class="badge bg-danger"
  810. style="cursor: pointer;"
  811. th:onclick="cancelBooking([[${booking.booking_id}]], [[${booking.mobile_no}]], [[${booking.booking_type}]])">Cancel
  812. Booking</span>
  813. </a>
  814. <!-- <a class="reschedule-button" th:if="${booking.booking_status == 'APPROVED' and booking.reason != 'Commercial'}"> -->
  815. <a class="reschedule-button"
  816. th:if="${booking.booking_status == 'APPROVED'
  817. and !#lists.contains({'Commercial', 'State Govt Event', 'Central Govt Event'}, booking.reason)}">
  818. <span class="badge bg-danger"
  819. style="cursor: pointer;"
  820. th:onclick="openRescheduleModal([[${booking.booking_id}]], [[${booking.start_date}]], [[${booking.end_date}]],[[${booking.no_of_days}]],
  821. [[${booking.hall_details_hall_id}]],[[${booking.starting_slot}]],[[${booking.ending_slot}]],[[${booking.reason}]])">Reschedule
  822. Booking</span>
  823. </a>
  824. <a class="reschedule-button"
  825. th:if="${booking.booking_status == 'WAITING_FOR_NOC'}">
  826. <span class="badge bg-danger"
  827. style="cursor: pointer;"
  828. th:onclick="openRescheduleModal([[${booking.booking_id}]], [[${booking.start_date}]], [[${booking.end_date}]],[[${booking.no_of_days}]],
  829. [[${booking.hall_details_hall_id}]],[[${booking.starting_slot}]],[[${booking.ending_slot}]],[[${booking.reason}]])">Reschedule
  830. Booking</span>
  831. </a>
  833. </p>
  835. </td>
  838. <td>
  839. <a class="view-button">
  840. <!-- <span class="badge bg-primary"
  841. style="cursor: pointer;"
  842. th:onclick="showBookingDetails([[${booking.booking_id}]])">View</span>-->
  843. <span class="badge bg-primary"
  844. style="cursor: pointer;"
  845. th:onclick="showBookingDetails([[${booking.booking_id}]], [[${bookingRefIds[booking.booking_id]}]])">
  846. View
  847. </span>
  849. </a>
  850. <!--<a class="view-button">
  851. <span class="badge bg-primary"
  852. style="cursor: pointer;"
  853. th:onclick="trackBooking([[${booking.booking_id}]])">Track</span>
  854. </a>-->
  855. </td>
  856. </tr>
  857. </tbody>
  858. </table>
  859. </div>
  860. </div>
  862. </div>
  864. <input type="hidden" id="serverDate" th:value=${serverDate}>
  871. <div class="modal fade backdrop" id="showBookingDetails" data-backdrop="static"
  872. tabindex="-1" role="dialog" aria-labelledby="staticBackdropLabel"
  873. aria-hidden="true">
  877. <div class="modal-dialog modal-lg" role="document">
  878. <div class="modal-content" id="printableContent">
  880. <form id="regform" onsubmit="return rejectsubmit();">
  881. <!--ak-->
  882. <!-- Add these -->
  883. <input type="hidden" id="modalBookingId">
  884. <input type="hidden" id="modalRefId">
  885. <div
  886. class="block block-rounded block-themed block-transparent mb-0">
  888. <div class="block-header bg-primary-dark">
  889. <h3 class="block-title" id="2mtitle">Booking
  890. Information</h3>
  891. <div class="block-options">
  892. <button type="button" class="btn-block-option"
  893. data-bs-dismiss="modal" aria-label="Close">
  894. <i class="fa fa-fw fa-times"></i>
  895. </button>
  896. </div>
  897. </div>
  899. <div class="block-content row"
  900. style="margin-right:0px;margin:0;padding:0;">
  901. <div class="col-md-12 col-lg-12 col-sm-12">
  902. <div class="card-body">
  903. <table>
  904. <tr>
  905. <th colspan="10"
  906. style="background-color: lightgrey;">
  907. User Details
  908. </th>
  909. </tr>
  910. <tr>
  911. <th
  912. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  913. User Name:
  914. </th>
  915. <td class="fw-semibold"
  916. style="padding: 0.45rem 0.45rem;"
  917. id="td_userName"></td>
  918. <th
  919. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  920. Mobile Number:
  921. </th>
  922. <td class="fw-semibold"
  923. style="padding: 0.45rem 0.45rem;"
  924. id="td_mobileNumber"></td>
  926. <th
  927. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  928. User Type:
  929. </th>
  930. <td class="fw-semibold"
  931. style="padding: 0.45rem 0.45rem;"
  932. id="td_usertype"></td>
  934. </tr>
  935. <tr>
  936. <th
  937. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  938. User Address:
  939. </th>
  940. <td colspan="5" class="fw-semibold"
  941. style="padding: 0.45rem 0.45rem;text-wrap: pretty;"
  942. id="td_useraddress"></td>
  944. </tr>
  945. <input type="hidden"
  946. class="form-control text-center"
  947. name="bookingid" id="bookingid" disabled />
  948. <tr>
  949. <th colspan="10"
  950. style="background-color: lightgrey;">
  951. Hall Details
  952. </th>
  953. </tr>
  955. <tr>
  956. <th
  957. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  958. Hall Name:
  959. </th>
  960. <td colspan="10" class="fw-semibold"
  961. style="padding: 0.45rem 0.45rem;text-wrap:pretty;"
  962. id="td_hallName"></td>
  964. </tr>
  965. <th
  966. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  967. Hall Address:
  968. </th>
  969. <td colspan="10" class="fw-semibold"
  970. style="padding: 0.45rem 0.45rem;text-wrap: pretty;"
  971. id="td_halladdress"></td>
  973. </tr>
  974. <tr>
  975. <th
  976. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  977. Caretaker Name:
  978. </th>
  979. <td colspan="2" class="fw-semibold"
  980. style="padding: 0.45rem 0.45rem;"
  981. id="td_caretakername"></td>
  982. <th
  983. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  984. Caretaker Mobile Number:
  985. </th>
  986. <td colspan="2" class="fw-semibold"
  987. style="padding: 0.45rem 0.45rem;"
  988. id="td_caretakermobileNumber"></td>
  990. </tr>
  991. <tr>
  992. <th colspan="10"
  993. style="background-color: lightgrey;">
  994. Booking
  995. Details (Booking Id:-<span
  996. id="booking_id"
  997. style="color:blue"></span>)
  998. </th>
  999. </tr>
  1000. <tr>
  1001. <th
  1002. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1003. Booking Date:
  1004. </th>
  1005. <td colspan="2" class="fw-semibold"
  1006. style="padding: 0.45rem 0.45rem;"
  1007. id="td_bookingDate"></td>
  1008. <th
  1009. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1010. Deposit Amount (in Rs):
  1011. </th>
  1012. <td colspan="2"
  1013. class="fw-semibold amount-cell"
  1014. style="padding: 0.45rem 0.45rem;"
  1015. id="td_depositeAmount"></td>
  1016. </tr>
  1017. <tr>
  1018. <th
  1019. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1020. Start Date:
  1021. </th>
  1022. <td colspan="2" class="fw-semibold"
  1023. style="padding: 0.45rem 0.45rem;"
  1024. id="td_startDate"></td>
  1025. <th
  1026. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1027. Hall Amount (in Rs):
  1028. </th>
  1029. <td colspan="2"
  1030. class="fw-semibold amount-cell"
  1031. style="padding: 0.45rem 0.45rem;"
  1032. id="td_hallAmount"></td>
  1033. </tr>
  1034. <tr>
  1035. <th
  1036. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1037. END Date:
  1038. </th>
  1039. <td colspan="2" class="fw-semibold"
  1040. style="padding: 0.45rem 0.45rem;"
  1041. id="td_endDate"></td>
  1042. <th
  1043. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1044. GST @18% (in Rs):
  1045. </th>
  1046. <td colspan="2"
  1047. class="fw-semibold amount-cell"
  1048. style="padding: 0.45rem 0.45rem;"
  1049. id="td_gst"></td>
  1050. </tr>
  1051. <tr>
  1052. <th
  1053. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1054. Starting Slot:
  1055. </th>
  1056. <td colspan="2" class="fw-semibold"
  1057. style="padding: 0.45rem 0.45rem;"
  1058. id="td_startingSlot"></td>
  1059. <th
  1060. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1061. Total Amount (in Rs):
  1062. </th>
  1063. <td colspan="2"
  1064. class="fw-semibold amount-cell"
  1065. style="padding: 0.45rem 0.45rem;"
  1066. id="td_totalAmount"></td>
  1067. </tr>
  1068. <tr>
  1069. <th
  1070. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1071. Ending Slot:
  1072. </th>
  1073. <td colspan="2" class="fw-semibold"
  1074. style="padding: 0.45rem 0.45rem;"
  1075. id="td_endingSlot"></td>
  1076. <!--<th style="display:none;padding: 0.45rem 0.45rem;border:none"
  1077. id="rejectionreasondiv">Rejection
  1078. Reason:</th>
  1079. <td class="fw-semibold"
  1080. style="padding: 0.45rem 0.45rem;"
  1081. id="reasonforrejection"></td>-->
  1083. <th
  1084. style="padding: 0.45rem 0.45rem;border:none">
  1085. Booking Status:
  1086. </th>
  1087. <td colspan="2" class="fw-semibold"
  1088. style="padding: 0.45rem 0.45rem;text-wrap: pretty;"
  1089. id="bookingstatus_td"></td>
  1090. </tr>
  1091. <tr>
  1092. <th style="display:none;padding: 0.45rem 0.45rem;border:none"
  1093. id="rejectionreasondiv">Rejection
  1094. Reason:
  1095. </th>
  1096. <td class="fw-semibold"
  1097. style="padding: 0.45rem 0.45rem;text-wrap: pretty;"
  1098. id="reasonforrejection"></td>
  1099. </tr>
  1100. </table>
  1101. </div>
  1102. </div>
  1103. <div class="row col-md-12 col-lg-12 col-sm-12"
  1104. style="margin-left:6px;margin-top:-21px">
  1105. <div class="documents" id="documents"></div>
  1106. </div>
  1107. <div class="col-md-12 col-lg-12 col-sm-12 mb-2"
  1108. id="paymentsdetails"
  1109. style="display:none; margin-top: -26px;">
  1110. <div class="card-body">
  1111. <table>
  1112. <tr>
  1113. <th colspan="10"
  1114. style="background-color: lightgrey;">
  1115. Booking Payment Details
  1116. </th>
  1117. </tr>
  1118. <tr>
  1119. <th
  1120. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  1121. Transaction ID:
  1122. </th>
  1123. <td colspan="10" class="fw-semibold"
  1124. style="padding: 0.45rem 0.45rem;"
  1125. id="td_transactionId"></td>
  1127. </tr>
  1128. <th
  1129. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  1130. Amount Received (in Rs):
  1131. </th>
  1132. <td colspan="10" class="fw-semibold"
  1133. style="padding: 0.45rem 0.45rem;"
  1134. id="td_payamountReceived"></td>
  1136. </tr>
  1137. <tr>
  1138. <th
  1139. style="padding: 0.45rem 0.45rem;font-weight: normal;">
  1140. Transaction Status:
  1141. </th>
  1142. <td class="fw-semibold"
  1143. style="padding: 0.45rem 0.45rem;"
  1144. id="td_paymentStatus"></td>
  1145. </tr>
  1146. </table>
  1147. </div>
  1148. </div>
  1149. <div class="row col-md-12 col-lg-12 col-sm-12"
  1150. id="ebdetails"
  1151. style="display:none;margin-left: 0px;margin-top: -49px">
  1152. <div class="card-body">
  1153. <table>
  1154. <tr>
  1155. <th colspan="4"
  1156. style="background-color: lightgrey;">EB
  1157. Details
  1158. </th>
  1159. </tr>
  1160. <tr>
  1161. <th
  1162. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1163. Consumer Number:
  1164. </th>
  1165. <td class="fw-semibold"
  1166. style="padding: 0.45rem 0.45rem;"
  1167. id="td_EBNumber"></td>
  1168. <th
  1169. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1170. EB Amount Per Unit (in Rs):
  1171. </th>
  1172. <td class="fw-semibold"
  1173. style="padding: 0.45rem 0.45rem;"
  1174. id="td_ebamountperunit"></td>
  1175. </tr>
  1176. <tr>
  1177. <th
  1178. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1179. Start Reading:
  1180. </th>
  1181. <td class="fw-semibold"
  1182. style="padding: 0.45rem 0.45rem;"
  1183. id="td_startingReading"></td>
  1184. <th
  1185. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1186. Unit Consumed:
  1187. </th>
  1188. <td class="fw-semibold"
  1189. style="padding: 0.45rem 0.45rem;"
  1190. id="td_usedunit"></td>
  1191. </tr>
  1192. <tr>
  1193. <th
  1194. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1195. END Reading:
  1196. </th>
  1197. <td class="fw-semibold"
  1198. style="padding: 0.45rem 0.45rem;"
  1199. id="td_endingReading"></td>
  1200. <th
  1201. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1202. EB Amount (in Rs):
  1203. </th>
  1204. <td class="fw-semibold"
  1205. style="padding: 0.45rem 0.45rem;"
  1206. id="td_electricityamount"></td>
  1207. </tr>
  1208. </tbody>
  1209. </table>
  1210. </div>
  1211. </div>
  1212. <div class="row col-md-12 col-lg-12 col-sm-12"
  1213. id="damagelist" style="disaply:none">
  1214. <div id="damageDetails"></div>
  1215. </div>
  1217. <div class="col-md-12 col-lg-12 col-sm-12"
  1218. id="refunddetails" style="margin-top:-41px">
  1219. <div class="card-body">
  1220. <table>
  1221. <tr>
  1222. <th colspan="2"
  1223. style="background-color: lightgrey;">
  1224. Amount to be Refunded (in Rs)
  1225. </th>
  1226. </tr>
  1227. <tr>
  1228. <th
  1229. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1230. Deposit Amount:
  1231. </th>
  1232. <td class="fw-semibold amount-cell"
  1233. style="padding: 0.45rem 0.45rem;"
  1234. id="td_depositeamountforrefund">0
  1235. </td>
  1236. </tr>
  1237. <tr>
  1238. <th
  1239. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1240. EB Amount:
  1241. </th>
  1242. <td class="fw-semibold amount-cell"
  1243. style="padding: 0.45rem 0.45rem;"
  1244. id="td_ebAmount"></td>
  1245. </tr>
  1246. <tr>
  1247. <th
  1248. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1249. Damage Amount:
  1250. </th>
  1251. <td class="fw-semibold amount-cell"
  1252. style="padding: 0.45rem 0.45rem;"
  1253. id="td_damage"></td>
  1254. </tr>
  1255. <tr id="pendingcolumn">
  1256. <th id="th_settel_label"
  1257. style="padding: 0.45rem 0.45rem; background-color: #f2f2f2;font-weight: normal">
  1258. Collection Pending Amount:
  1259. </th>
  1260. <td class="fw-semibold amount-cell"
  1261. style="padding: 0.45rem 0.45rem; color: green;"
  1262. id="td_pending_amt">0
  1263. </td>
  1264. </tr>
  1265. <tr id="collectionstatuscolumn">
  1266. <th id="label"
  1267. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1268. Collection Pending Status
  1269. :
  1270. </th>
  1271. <td class="fw-semibold amount-cell"
  1272. style="padding: 0.45rem 0.45rem; color: green;"
  1273. id="td_collection_status">
  1274. </td>
  1275. </tr>
  1276. <tr>
  1277. <th
  1278. style="padding: 0.45rem 0.45rem; background-color: #f2f2f2;font-weight: normal">
  1279. Actual refundable Amount:
  1280. </th>
  1281. <td class="fw-semibold amount-cell"
  1282. style="padding: 0.45rem 0.45rem; color: green;"
  1283. id="td_settel_amt">0
  1284. </td>
  1285. </tr>
  1286. </table>
  1287. </div>
  1288. </div>
  1289. <div class="row col-md-12 col-lg-12 col-sm-12"
  1290. id="refundamountDetails"
  1291. style="display:none;margin-left: 0px;margin-top: -49px">
  1292. <div class="card-body">
  1293. <table>
  1294. <tr>
  1295. <th colspan="4"
  1296. style="background-color: lightgrey;">
  1297. Refund Details
  1298. </th>
  1299. </tr>
  1300. <tr>
  1301. <th
  1302. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1303. Booking Status:
  1304. </th>
  1305. <td class="fw-semibold"
  1306. style="padding: 0.45rem 0.45rem;"
  1307. id="td_bookingStatus"></td>
  1308. <th
  1309. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1310. Refund Status:
  1311. </th>
  1312. <td class="fw-semibold"
  1313. style="padding: 0.45rem 0.45rem;"
  1314. id="td_refundStatus"></td>
  1315. </tr>
  1316. <tr>
  1317. <th
  1318. style="padding: 0.45rem 0.45rem;font-weight: normal;text-wrap: pretty;">
  1319. Refund amount:
  1320. </th>
  1321. <td class="fw-semibold" colspan="5"
  1322. style="padding: 0.45rem 0.45rem;"
  1323. id="td_refundamount"></td>
  1324. </tr>
  1325. </tbody>
  1326. </table>
  1327. </div>
  1328. </div>
  1329. <div id="refundMessage" style="display: none;">
  1330. <h1 id="refundText"
  1331. style="font-size: 17px;margin-left: 20px;color: darkgreen;">
  1332. </h1>
  1333. </div>
  1334. <div id="rejectrefundMessage" style="display: none;">
  1335. <h1 id="rejectrefundText"
  1336. style="font-size: 17px;margin-left: 20px;color: darkgreen;">
  1337. </h1>
  1338. </div>
  1339. <div id="blockedrefundMessage" style="display: none;">
  1340. <h1 id="blockedrefundText"
  1341. style="font-size: 17px;margin-left: 20px;color: darkgreen;">
  1342. </h1>
  1343. </div>
  1344. <!--Newly added for Reschedule Details-->
  1345. <!--<div class="row col-md-12 col-lg-12 col-sm-12"
  1346. id="rescheduleDetails"
  1347. style="display:none;margin-left: 0px;margin-top: -49px">
  1348. <div class="card-body">
  1349. <table>
  1350. <tr>
  1351. <th colspan="4"
  1352. style="background-color: lightgrey;">
  1353. Reschedule Details
  1354. </th>
  1355. </tr>
  1356. <tr>
  1357. <th
  1358. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1359. Event Start Date:
  1360. </th>
  1361. <td class="fw-semibold"
  1362. style="padding: 0.45rem 0.45rem;"
  1363. id="td_res_start_date"></td>
  1364. <th
  1365. style="padding: 0.45rem 0.45rem;font-weight: normal">
  1366. Event End Date:
  1367. </th>
  1368. <td class="fw-semibold"
  1369. style="padding: 0.45rem 0.45rem;"
  1370. id="td_res_end_date"></td>
  1371. </tr>
  1372. <tr>
  1373. <th
  1374. style="padding: 0.45rem 0.45rem;font-weight: normal;text-wrap: pretty;">
  1375. Rescheduled Date:</th>
  1376. <td class="fw-semibold" colspan="5"
  1377. style="padding: 0.45rem 0.45rem;"
  1378. id="td_res_date"></td>
  1379. </tr>
  1380. </tbody>
  1381. </table>
  1382. </div>
  1383. </div>-->
  1384. </div>
  1386. </div>
  1387. <div class="block-content block-content-full text-end bg-body"
  1388. id="mbutton">
  1389. <button class="btn btn-success"
  1390. onclick="downloadAcknowledgment(event)"
  1391. style="background: #FB6340;">View
  1392. Acknowledgement
  1393. </button>
  1394. <button type="button"
  1395. style="background-color: rgb(21,69,93);color: white;"
  1396. class="btn btn-sm btn-alt-secondary"
  1397. data-bs-dismiss="modal">Close
  1398. </button>
  1399. </div>
  1400. </form>
  1401. </div>
  1402. </div>
  1403. </div>
  1404. </div>
  1405. <br>
  1406. </div>
  1407. </div>
  1408. <div class="modal fade" id="fileModal" tabindex="-1" role="dialog"
  1409. aria-labelledby="fileModalLabel" aria-hidden="true">
  1410. <div class="modal-dialog modal-lg" role="document">
  1411. <div class="modal-content">
  1412. <div class="modal-header">
  1413. <h5 class="modal-title" id="fileModalLabel">File Preview</h5>
  1414. <button type="button" class="close" data-bs-dismiss="modal" aria-label="Close"
  1415. style="border: 1px solid black; padding: 5px;
  1416. display: inline-flex; align-items: center; justify-content: center;
  1417. background-color: transparent; color: black; font-size: 20px;">
  1418. <span aria-hidden="true">&times;</span>
  1419. </button>
  1420. </div>
  1421. <div class="modal-body">
  1422. <embed id="filePreview" src="" width="100%" height="600px">
  1423. </div>
  1424. <div class="modal-footer">
  1425. <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close
  1426. </button>
  1427. </div>
  1428. </div>
  1429. </div>
  1430. </div>
  1431. </div>
  1432. <!-- Reschedule Booking Modal -->
  1433. <div class="modal fade" id="bookingRescheduleModal" tabindex="-1"
  1434. aria-labelledby="bookingModalLabel" aria-hidden="true">
  1435. <div class="modal-dialog modal-dialog-centered modal-lg">
  1436. <div class="modal-content">
  1437. <!-- Modal Header -->
  1438. <div class="modal-header" style="color:black">
  1439. <h5 class="modal-title" id="bookingModalLabel" style="color:black">Booking
  1440. Reschedule</h5>
  1441. <br>
  1442. <br>
  1443. <div style="margin-bottom: -59px; margin-left: -185px;">
  1444. <!-- Adding margin-top for separation -->
  1445. <p style="font-size: 14px; color: #6c757d;"> the Start Date & Slot can be
  1446. changed.</p>
  1447. </div>
  1448. <button type="button" class="btn-close" data-bs-dismiss="modal"
  1449. aria-label="Close"></button>
  1450. </div>
  1452. <!-- Modal Body -->
  1453. <div class="modal-body">
  1454. <div class="container-fluid">
  1455. <div class="row">
  1456. <!-- Datepicker and Availability Buttons Column -->
  1457. <div id="datepicker-container" class="fixedcontainer"></div>
  1459. <!-- Start Date, End Date, Number of Days Inputs Column -->
  1460. <div class="col">
  1461. <input type="hidden" class="form-control" id="bookingId"
  1462. name="bookingId" required>
  1463. <label for="startDateInput" class="form-label">Start Date:</label>
  1464. <input type="text" class="form-control" id="startDateInput"
  1465. name="startDateInput" required readonly>
  1466. <input type="hidden" class="form-control" id="startDatetext"
  1467. name="startDatetext" required>
  1468. </div>
  1469. <div class="col">
  1470. <label for="endDateInput" class="form-label">End Date:</label>
  1471. <input type="date" class="form-control" id="endDateInput"
  1472. name="endDateInput" readonly>
  1473. </div>
  1474. <div class="col">
  1475. <label for="noOfDaysInput" class="form-label">Number of Days:</label>
  1476. <input type="number" class="form-control" id="noOfDaysInput"
  1477. name="noOfDaysInput" readonly>
  1478. </div>
  1479. </div>
  1480. <div class="row">
  1481. <div class="col">
  1482. <input type="hidden" id="daysDiff">
  1483. <label for="startingSlot" class="form-label">Starting Slot:</label>
  1484. <select class="form-control" id="startingSlot" name="startingSlot">
  1485. <option value="1">Morning (6:00 AM)</option>
  1486. <option value="2">Afternoon (2:00 PM)</option>
  1487. </select>
  1488. </div>
  1489. <div class="col">
  1490. <label for="endingSlot" class="form-label">Ending Slot:</label>
  1491. <select class="form-control" id="endingSlot" name="endingSlot" disabled>
  1492. <option value="1">Afternoon (2:00 PM)</option>
  1493. <option value="2">Evening (10:00 PM)</option>
  1494. </select>
  1495. <!-- mirrors endingSlot for form submission since disabled fields are excluded -->
  1496. <input type="hidden" id="endingSlotHidden" name="endingSlot">
  1497. </div>
  1498. </div>
  1499. <div class="row" style="margin-top: 39px;">
  1500. <div class="col col-lg-2 col-sm-2 col-md-2">
  1501. <button type="button" class="btn btn-primary btn-square-md"
  1502. style="background-color:#008000;"></button>
  1503. <p style="margin-left: 14px;">Day<br>(Available)</p>
  1504. </div>
  1505. <div class="col col-lg-2 col-sm-2 col-md-2">
  1506. <button type="button" class="btn btn-primary btn-square-md"
  1507. style="background-color: #ac2bac;"></button>
  1508. <p style="margin-left: 14px;">Morning<br>(Available)</p>
  1509. </div>
  1510. <div class="col col-lg-2 col-sm-2 col-md-2">
  1511. <button type="button" class="btn btn-primary btn-square-md"
  1512. style="background-color:#FFEA00;"></button>
  1513. <p style="margin-left: 14px;">Evening<br>(Available)</p>
  1514. </div>
  1515. <div class="col col-lg-2 col-sm-2 col-md-2">
  1516. <button type="button" class="btn btn-primary btn-square-md"
  1517. style="background-color: red;"></button>
  1518. <p style="margin-left: 14px;">Not Available</p>
  1519. </div>
  1520. <div class="col col-lg-2 col-sm-2 col-md-2">
  1521. <button type="button" class="btn btn-primary btn-square-md"
  1522. style="background-color: blue;"></button>
  1523. <p style="margin-left: 14px;">GCC Blocked</p>
  1524. </div>
  1525. <!--<div class="col col-lg-2 col-sm-2 col-md-2">
  1526. <button type="button" class="btn btn-primary btn-square-md"
  1527. style="background-color: lightpink;"></button>
  1528. <p style="margin-left: 14px;">Temporary Blocked</p>
  1529. </div>-->
  1530. </div>
  1531. </div>
  1532. </div>
  1533. <!-- Modal Footer -->
  1534. <div class="modal-footer">
  1535. <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close
  1536. </button>
  1537. <button type="button" class="btn btn-primary" onclick="Reschedule()">Save
  1538. Changes
  1539. </button>
  1540. </div>
  1541. </div>
  1542. </div>
  1543. </div>
  1545. <!-- Reschedule OTP Verification Modal -->
  1546. <div class="modal fade" id="rescheduleOtpModal" tabindex="-1" role="dialog"
  1547. aria-labelledby="rescheduleOtpModalLabel" aria-hidden="true">
  1548. <div class="modal-dialog" role="document">
  1549. <div class="modal-content">
  1550. <div class="modal-header">
  1551. <h6 class="modal-title m-0" id="rescheduleOtpModalLabel">Reschedule Verification
  1552. </h6>
  1553. <button type="button" class="btn-close" data-bs-dismiss="modal"
  1554. aria-label="Close"></button>
  1555. </div>
  1556. <div class="modal-body">
  1557. <div class="row">
  1558. <div class="mb-3 text-center">
  1559. <img src="media/images/mobileotp.png" width="50%" alt="Mobileotp">
  1560. </div>
  1561. <div class="mb-0 text-center">
  1562. <h4>OTP Verification</h4>
  1563. <p class="text-mute">Enter the OTP sent to <b class="text-info"
  1564. id="rescheduleMobileTxt"></b></p>
  1565. <p class="text-danger" id="rescheduleOtpError"></p>
  1566. </div>
  1567. <div class="mb-3 text-center">
  1568. <div class="otp-input-box">
  1569. <input type="text" maxlength="1" class="otp-input" id="rescheduleOtp1"
  1570. required />
  1571. <input type="text" maxlength="1" class="otp-input" id="rescheduleOtp2"
  1572. required />
  1573. <input type="text" maxlength="1" class="otp-input" id="rescheduleOtp3"
  1574. required />
  1575. <input type="text" maxlength="1" class="otp-input" id="rescheduleOtp4"
  1576. required />
  1577. <input type="text" maxlength="1" class="otp-input" id="rescheduleOtp5"
  1578. required />
  1579. </div>
  1580. </div>
  1581. <div class="mb-3 text-center">
  1582. <div id="rescheduleResendContainer">
  1583. <p class="mb-0">Didn't receive OTP?</p>
  1584. <!-- <p class="mb-0 text-info" id="rescheduleResendLink">Please wait..<span
  1585. id="rescheduleCountdown">60</span>s</p> -->
  1586. <p class="mb-0 text-info">
  1587. <span id="rescheduleResendText">Please wait..</span>
  1588. <span id="rescheduleCountdown">60</span>s
  1589. </p>
  1590. </div>
  1591. </div>
  1592. </div>
  1593. </div>
  1594. <div class="modal-footer">
  1595. <button type="button" class="btn btn-secondary btn-sm"
  1596. data-bs-dismiss="modal">Close</button>
  1597. <button type="button" class="btn btn-primary btn-sm"
  1598. onclick="verifyRescheduleOtp()">Verify OTP</button>
  1599. </div>
  1600. </div>
  1601. </div>
  1602. </div>
  1604. <!-- Tracking Log Modal -->
  1605. <!-- Tracking Modal -->
  1606. <div class="modal fade" id="trackingModal" tabindex="-1" aria-labelledby="trackingModalLabel"
  1607. aria-hidden="true">
  1608. <div class="modal-dialog modal-lg">
  1609. <div class="modal-content">
  1610. <div class="modal-header">
  1611. <h4 class="modal-title">Booking Tracking</h4>
  1612. <button type="button" class="btn-close" data-bs-dismiss="modal"
  1613. aria-label="Close"></button>
  1614. </div>
  1615. <div class="modal-body">
  1616. <div class="tracking-container">
  1617. <ul id="trackingList" class="tracking-steps list-unstyled">
  1618. <!-- Steps will be dynamically appended here -->
  1619. </ul>
  1620. </div>
  1621. </div>
  1622. </div>
  1623. </div>
  1624. </div>
  1626. <!-- Modal -->
  1627. <div class="modal fade" id="uploadNocModal" tabindex="-1" aria-labelledby="uploadNocModalLabel"
  1628. aria-hidden="true">
  1629. <div class="modal-dialog">
  1630. <div class="modal-content">
  1631. <div class="modal-header">
  1632. <h5 class="modal-title" id="uploadNocModalLabel">Upload NOC</h5>
  1633. <button type="button" class="btn-close" data-bs-dismiss="modal"
  1634. aria-label="Close"></button>
  1635. </div>
  1636. <div class="modal-body">
  1637. <div class="mb-3">
  1638. <label for="nocFile" class="form-label">Select NOC File</label>
  1639. <input type="file" class="form-control nocfile" id="nocFile" name="nocFile"
  1640. required>
  1641. <input type="hidden" id="bookingssId" name="bookingssId">
  1642. </div>
  1643. </div>
  1644. <div class="modal-footer">
  1645. <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close
  1646. </button>
  1647. <button type="button" class="btn btn-primary" id="submitNocButton">Submit</button>
  1648. </div>
  1649. </div>
  1650. </div>
  1651. </div>
  1653. <!-- Modal -->
  1654. <div class="modal fade" id="transactionHistoryModal" tabindex="-1"
  1655. aria-labelledby="transactionHistoryModalLabel" aria-hidden="true">
  1656. <div class="modal-dialog modal-lg" id="transactionmodel"> <!-- modal-lg makes it larger -->
  1657. <div class="modal-content">
  1658. <div class="modal-header">
  1659. <h5 class="modal-title" id="transactionHistoryModalLabel">Transaction History</h5>
  1660. <button type="button" class="btn-close" data-bs-dismiss="modal"
  1661. aria-label="Close"></button>
  1662. </div>
  1663. <div class="modal-body">
  1664. <!-- Scrollable Table -->
  1665. <div class="table-responsive"> <!-- Make the table scrollable if too large -->
  1666. <table class="table table-bordered" id="transactionTable">
  1667. <thead>
  1668. <tr>
  1669. <th>S.NO</th>
  1670. <th>Booking ID</th>
  1671. <th>Amount</th>
  1672. <th>Date</th>
  1673. <th>Transaction ID</th>
  1674. <th>Status</th>
  1675. </tr>
  1676. </thead>
  1677. <tbody>
  1678. <!-- Data will be populated dynamically here -->
  1679. </tbody>
  1680. </table>
  1681. </div>
  1682. <div class="table-responsive" id="refunddetails" style="display: none;">
  1683. <h2>Refund Details</h2>
  1684. <table class="table table-bordered" id="refunddetailsTable">
  1685. <thead>
  1686. <tr>
  1687. <th>S.NO</th>
  1688. <th>Booking ID</th>
  1689. <th>Amount</th>
  1690. <th>Date</th>
  1691. <th>Transaction ID</th>
  1692. <th>Refund Amount</th>
  1693. </tr>
  1694. </thead>
  1695. <tbody>
  1696. <!-- Data will be populated dynamically here -->
  1697. </tbody>
  1698. </table>
  1699. </div>
  1701. </div>
  1702. <div class="modal-footer">
  1703. <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close
  1704. </button>
  1705. </div>
  1706. </div>
  1707. </div>
  1708. </div>
  1709. <footer th:replace="~{fragments/footer :: footer}"></footer>
  1710. </div>
  1711. </div>
  1712. </div>
  1714. <!--otp form-->
  1715. <div th:replace="~{fragments/loginreg :: div}"></div>
  1716. <!--otp form-->
  1717. <script src="js/html2pdf.bundle.min.js"></script>
  1718. <script th:replace="~{fragments/script :: script}"></script>
  1719. <script th:replace="~{fragments/logRegiOtpScript :: script}"></script>
  1720. <script type="text/javascript" src="https://www.paynimo.com/paynimocheckout/server/lib/checkout.js"></script>
  1721. <script src="https://cdn.datatables.net/1.13.4/js/jquery.dataTables.min.js"></script>
  1722. <script src="https://cdn.datatables.net/buttons/2.4.1/js/dataTables.buttons.min.js"></script>
  1723. <script src="https://cdn.datatables.net/buttons/2.4.1/js/buttons.html5.min.js"></script>
  1724. <script type="text/javascript">
  1725. // Reschedule variables
  1726. var rescheduleBookingId = null;
  1727. var rescheduleStartDate = null;
  1728. var rescheduleEndDate = null;
  1729. var rescheduleMobileNumber = null;
  1730. var rescheduleHallId = null;
  1731. var rescheduleStartingSlot = null;
  1732. var rescheduleEndingSlot = null;
  1733. var rescheduleReason = null;
  1735. $(document).ready(function () {
  1736. $('#detailstable').DataTable({
  1737. responsive: true,
  1738. pageLength: 10,
  1739. ordering: true,
  1740. columnDefs: [{
  1741. targets: 'no-sort',
  1742. orderable: false
  1743. }],
  1744. dom: 'Bfrtip',
  1745. buttons: [
  1746. {
  1747. extend: 'excelHtml5',
  1748. text: 'Export to Excel',
  1749. className: 'btn btn-primary'
  1750. }
  1751. ]
  1752. });
  1753. });
  1754. $(document).ready(function () {
  1755. $('#submitNocButton').on('click', function (e) {
  1756. e.preventDefault();
  1758. // Get the form data
  1759. var formData = new FormData();
  1760. var fileInput = $('#nocFile')[0].files[0]; // Get the selected file
  1761. var bookingssId = $('#bookingssId').val(); // Get the bookingId
  1763. // Check if a file is selected
  1764. if (!fileInput) {
  1765. Swal.fire({
  1766. icon: 'warning',
  1767. title: 'No File Selected',
  1768. text: 'Please select a file to upload.',
  1769. });
  1770. return;
  1771. }
  1773. // Append file and bookingId to formData
  1774. formData.append('nocFile', fileInput);
  1775. formData.append('bookingssId', bookingssId);
  1777. // Perform Ajax request
  1778. $.ajax({
  1779. url: '/communityhall/user/api/uploaddocs', // API endpoint
  1780. type: 'POST',
  1781. data: formData,
  1782. contentType: false,
  1783. processData: false,
  1784. success: function (response) {
  1785. // Show success message and refresh the page
  1786. Swal.fire({
  1787. icon: 'success',
  1788. title: 'Success',
  1789. text: 'NOC uploaded successfully!',
  1790. }).then(() => {
  1791. $('#uploadNocModal').modal('hide'); // Close the modal
  1792. location.reload(); // Refresh the page
  1793. });
  1794. },
  1795. error: function (xhr, status, error) {
  1796. // Show error message
  1797. Swal.fire({
  1798. icon: 'error',
  1799. title: 'Upload Failed',
  1800. text: 'Failed to upload NOC: ' + error,
  1801. });
  1802. }
  1803. });
  1804. });
  1806. // Populate bookingId when opening the modal
  1807. $('#uploadNocModal').on('show.bs.modal', function (event) {
  1808. var button = $(event.relatedTarget); // Button that triggered the modal
  1809. var bookingId = button.data('booking-id'); // Extract bookingId from the button
  1810. $('#bookingssId').val(bookingId); // Set the bookingId in the hidden input field
  1811. });
  1812. });
  1815. // Function to track booking
  1816. function trackBooking(bookingId) {
  1817. $.ajax({
  1818. url: '/communityhall/user/api/trackBooking',
  1819. method: 'GET',
  1820. data: { bookingId: bookingId }, // Send booking ID to the server
  1821. success: function (data) {
  1822. // console.log("Received tracking data:", data);
  1824. // Clear the list initially before appending steps
  1825. $('#trackingList').empty();
  1827. if (Array.isArray(data) && data.length > 0) {
  1828. // Show the modal first
  1829. $('#trackingModal').modal('show');
  1831. // Create a Set to track seen statuses
  1832. const seenStatuses = new Set();
  1834. // Append steps one by one
  1835. data.forEach((event) => {
  1836. // Append each step if it hasn't been seen before
  1837. if (!seenStatuses.has(event.status)) {
  1838. seenStatuses.add(event.status); // Add status to Set
  1839. appendStep(event); // Call to append the event step
  1840. }
  1841. });
  1842. } else {
  1843. // Show a message when no tracking events are available
  1844. $('#trackingList').append('<li class="no-events">No tracking events available.</li>');
  1845. }
  1846. },
  1847. error: function (xhr, status, error) {
  1848. console.error("Failed to fetch booking details:", status, error);
  1849. alert('Failed to fetch booking details. Please try again later.');
  1850. }
  1851. });
  1852. }
  1855. function appendStep(event) {
  1856. const formattedDate = moment(event.dateTime).isValid()
  1857. ? moment(event.dateTime).format('MMM DD, YYYY, h:mm A') // Format date using Moment.js
  1858. : 'Invalid date';
  1860. const statusClass = getStatusClass(event.status); // Get CSS class for the status
  1861. const statusIcon = getStatusIcon(event.status); // Get icon for the status
  1863. // Create and append a step element for each event
  1864. const stepElement = `
  1865. <li class="tracking-step ${statusClass}">
  1866. <div class="step-icon">
  1867. <i class="fas ${statusIcon}"></i> <!-- Add the icon -->
  1868. </div>
  1869. <div class="step-content">
  1870. <h5>${event.description || 'No Description Available'}</h5> <!-- Event description -->
  1871. <p class="step-date">${formattedDate}</p> <!-- Formatted date -->
  1872. </div>
  1873. </li>
  1874. `;
  1876. // Append the element to the list
  1877. $('#trackingList').append(stepElement);
  1878. }
  1880. function getStatusClass(status) {
  1881. switch (status) {
  1882. case 'PAYMENT_SUCCESS':
  1883. case 'APPROVED':
  1884. case 'EVENT_COMPLETED':
  1885. case 'COMPLETED':
  1886. return 'completed'; // Returns 'completed' class for these statuses
  1887. case 'SETTLEMENT_RAISING':
  1888. return 'waiting';
  1889. case 'CANCELED':
  1890. return 'cancelled';
  1891. case 'REJECTED':
  1892. return 'rejected';
  1893. case 'GCC_BLOCKED':
  1894. return 'gcc-blocked';
  1895. default:
  1896. return 'pending'; // Default class if status is unknown
  1897. }
  1898. }
  1900. function getStatusIcon(status) {
  1901. switch (status) {
  1902. case 'PAYMENT_SUCCESS':
  1903. return 'fa-check-circle'; // Icon for payment success
  1904. case 'APPROVED':
  1905. return 'fa-thumbs-up';
  1906. case 'EVENT_COMPLETED':
  1907. return 'fa-calendar-check';
  1908. case 'CANCELED':
  1909. return 'fa-ban';
  1910. case 'REJECTED':
  1911. return 'fa-times-circle';
  1912. case 'GCC_BLOCKED':
  1913. return 'fa-lock';
  1914. default:
  1915. return 'fa-clock'; // Default icon for pending steps
  1916. }
  1917. }
  1920. function showFutureEvents() {
  1921. document.getElementById('futureEventsContainer').style.display = 'block';
  1922. }
  1924. function downloadAcknowledgment(event) {
  1925. event.preventDefault();
  1926. var bookingId = document.getElementById("booking_id").innerHTML;
  1927. var refId = document.getElementById("modalRefId").value;
  1929. // Redirect to the acknowledgment URL in the same tab
  1930. window.location.href = '/communityhall/user/acknowledgement?bookingId=' + encodeURIComponent(bookingId);
  1931. // var refId = document.getElementById("ref_" + bookingId).value;
  1932. console.log("Ref ID: " + refId);
  1934. window.location.href = '/communityhall/user/acknowledgement?ref_id=' + encodeURIComponent(refId);
  1935. }
  1937. function getTimeSlot(slotValue) {
  1938. var timeSlot;
  1939. var trimmedSlotValue = String(slotValue).trim(); // Convert to string and then trim
  1940. if (trimmedSlotValue === '1') {
  1941. timeSlot = 'Morning';
  1942. } else if (trimmedSlotValue === '2') {
  1943. timeSlot = 'Evening';
  1944. } else {
  1945. timeSlot = 'Unknown';
  1946. }
  1947. return timeSlot;
  1948. }
  1950. // function showBookingDetails(bookingId) {
  1951. function showBookingDetails(bookingId, refId) {
  1952. $.ajax({
  1953. url: '/communityhall/user/api/viewAllBookingDetails',
  1954. method: 'GET',
  1955. data: { bookingId: bookingId },
  1956. success: function (response) {
  1957. document.getElementById("td_userName").innerHTML = response.users.name;
  1958. document.getElementById("td_mobileNumber").innerHTML = response.users.mobileNo;
  1959. document.getElementById("td_usertype").innerHTML = response.users.usertype;
  1960. var userDetails = response.users;
  1961. var userDetailsString =
  1962. userDetails.doorNo + ", " +
  1963. userDetails.street + ", " +
  1964. userDetails.area + ", " +
  1965. userDetails.location + " ,Chennai- " +
  1966. userDetails.pinCode;
  1967. document.getElementById("td_useraddress").innerHTML = userDetailsString;
  1968. document.getElementById("td_hallName").innerHTML = response.hallDetails.hallName;
  1969. var hallDetails = response.hallDetails;
  1970. var hallDetailsString =
  1971. hallDetails.doorNo + ", " +
  1972. hallDetails.street + ", " +
  1973. hallDetails.area + ", " +
  1974. hallDetails.city + "- " +
  1975. hallDetails.pinCode;
  1976. document.getElementById("td_halladdress").innerHTML = hallDetailsString;
  1977. document.getElementById("td_caretakername").innerHTML = response.hallDetails.hallInchargeName;
  1978. document.getElementById("td_caretakermobileNumber").innerHTML = response.hallDetails.hallInchargeMobno;
  1979. document.getElementById("td_bookingDate").innerHTML = response.bookingDate;
  1980. document.getElementById("td_depositeAmount").innerHTML = parseFloat(response.depositAmount).toFixed(2);
  1981. document.getElementById("td_hallAmount").innerHTML = parseFloat(response.hallAmount).toFixed(2);
  1982. // Calculate GST and total amount
  1983. var gstAmount = (parseFloat(response.hallAmount) * (response.hallDetails.gst / 100)).toFixed(2);
  1984. var totalAmount = parseFloat(response.amountReceived).toFixed(2);
  1986. document.getElementById("td_gst").innerHTML = gstAmount;
  1987. document.getElementById("td_totalAmount").innerHTML = totalAmount;
  1989. document.getElementById("td_startDate").innerHTML = response.startDate;
  1990. document.getElementById("td_endDate").innerHTML = response.endDate;
  1991. document.getElementById("booking_id").innerHTML = response.bookingId;
  1994. function getTimeSlot(slotValue) {
  1995. var timeSlot;
  1996. var trimmedSlotValue = String(slotValue).trim(); // Convert to string and then trim
  1997. if (trimmedSlotValue === '1') {
  1998. timeSlot = 'Morning';
  1999. } else if (trimmedSlotValue === '2') {
  2000. timeSlot = 'Evening';
  2001. } else {
  2002. timeSlot = 'Unknown';
  2003. }
  2004. return timeSlot;
  2005. }
  2007. document.getElementById("td_startingSlot").innerHTML = getTimeSlot(response.startingSlot);
  2008. document.getElementById("td_endingSlot").innerHTML = getTimeSlot(response.endingSlot);
  2009. document.getElementById("bookingstatus_td").innerHTML = response.bookingStatus;
  2011. console.log("before comments user view history...");
  2012. console.log("Comments..." + response.comments);
  2014. if (response.bookingStatus === 'REJECTED' && response.comments) {
  2015. document.getElementById("rejectionreasondiv").style.display = "block";
  2016. const rejectionCell = document.getElementById("reasonforrejection");
  2017. rejectionCell.innerHTML = response.comments;
  2018. } else {
  2019. document.getElementById("rejectionreasondiv").style.display = "none";
  2020. document.getElementById("reasonforrejection").style.display = "none";
  2021. }
  2022. showReasonDocuments(response);
  2024. if (response.payments) {
  2025. document.getElementById("paymentsdetails").style.display = "block";
  2026. document.getElementById("td_transactionId").innerHTML = response.payments.transactionId;
  2027. document.getElementById("td_payamountReceived").innerHTML = response.payments.amountReceived;
  2028. document.getElementById("td_paymentStatus").innerHTML = response.payments.paymentStatus;
  2029. } else {
  2030. document.getElementById("paymentsdetails").style.display = "none";
  2031. }
  2032. if (response.ebDetails) {
  2033. document.getElementById("ebdetails").style.display = "block";
  2034. document.getElementById("td_EBNumber").innerHTML = response.hallDetails.ebNumber;
  2035. document.getElementById("td_startingReading").innerHTML = response.ebDetails.startingReading;
  2036. document.getElementById("td_endingReading").innerHTML = response.ebDetails.endingReading;
  2037. document.getElementById("td_usedunit").innerHTML = response.ebDetails.usedUnit;
  2038. document.getElementById("td_ebamountperunit").innerHTML = parseFloat(response.hallDetails.ebCostPerUnit).toFixed(2);
  2039. document.getElementById("td_electricityamount").innerHTML = parseFloat(response.ebDetails.ebAmount).toFixed(2);
  2041. } else {
  2042. document.getElementById("ebdetails").style.display = "none";
  2043. }
  2044. if (response.damageList && response.damageList.length > 0) {
  2045. document.getElementById("damagelist").style.display = "block";
  2047. } else {
  2048. document.getElementById("damagelist").style.display = "none";
  2049. }
  2050. if (response.settlement) {
  2051. document.getElementById("refunddetails").style.display = "block";
  2052. document.getElementById("td_depositeamountforrefund").innerHTML = parseFloat(response.depositAmount).toFixed(2);
  2053. document.getElementById("td_electricityamount").innerHTML = parseFloat(response.ebDetails.ebAmount).toFixed(2);
  2054. document.getElementById("td_ebAmount").innerHTML = parseFloat(response.ebDetails.ebAmount).toFixed(2);
  2055. document.getElementById("td_damage").innerHTML = parseFloat(response.settlement.damageAmount).toFixed(2);
  2057. var eb_amt = parseFloat(response.ebDetails.ebAmount).toFixed(2);
  2058. var deposit_amt = parseFloat(response.depositAmount).toFixed(2);
  2059. var tem_total = (deposit_amt - eb_amt).toFixed(2);
  2060. $("#td_settel_amt").html(tem_total);
  2061. } else {
  2062. document.getElementById("refunddetails").style.display = "none";
  2063. }
  2065. showDamageDetails(response);
  2066. if (response.bookingStatus === 'CANCELED' && ['WAITING', 'APPROVED', 'INITIATED'].includes(response.refundStatus)) {
  2067. document.getElementById("td_refundamount").innerHTML = `Your booking has been cancelled. Deposit amount of ₹ ${parseFloat(response.depositAmount).toFixed(2)} will be refund 3 to 15 Days`;
  2068. document.getElementById("refundamountDetails").style.display = "block";
  2069. document.getElementById("td_bookingStatus").innerHTML = response.bookingStatus;
  2070. document.getElementById("td_refundStatus").innerHTML = response.refundStatus;
  2071. } else if (response.bookingStatus === 'CANCELED' && response.refundStatus === 'COMPLETED') {
  2072. document.getElementById("td_refundamount").innerHTML = `Deposit amount of ₹ ${parseFloat(response.depositAmount).toFixed(2)} refunded successfully`;
  2073. document.getElementById("refundamountDetails").style.display = "block";
  2074. document.getElementById("td_bookingStatus").innerHTML = response.bookingStatus;
  2075. document.getElementById("td_refundStatus").innerHTML = response.refundStatus;
  2076. } else if (response.bookingStatus === 'REJECTED' && ['WAITING', 'APPROVED', 'INITIATED'].includes(response.refundStatus) && response.amountReceived == 0) {
  2077. document.getElementById("refundamountDetails").style.display = "none";
  2078. } else if (response.bookingStatus === 'REJECTED' && ['WAITING', 'APPROVED', 'INITIATED'].includes(response.refundStatus)) {
  2079. document.getElementById("td_refundamount").innerHTML = `Your booking has been Rejected by GCC. Full amount of ₹ ${parseFloat(response.amountReceived).toFixed(2)} will be refunded shortly`;
  2080. document.getElementById("refundamountDetails").style.display = "block";
  2081. document.getElementById("td_bookingStatus").innerHTML = response.bookingStatus;
  2082. document.getElementById("td_refundStatus").innerHTML = response.refundStatus;
  2083. } else if (response.bookingStatus === 'REJECTED' && response.refundStatus === 'COMPLETED') {
  2084. document.getElementById("td_refundamount").innerHTML = `Full amount of ₹${parseFloat(response.amountReceived).toFixed(2)} refunded successfully`;
  2085. document.getElementById("refundamountDetails").style.display = "block";
  2086. document.getElementById("td_bookingStatus").innerHTML = response.bookingStatus;
  2087. document.getElementById("td_refundStatus").innerHTML = response.refundStatus;
  2088. } else if (response.bookingStatus === 'REJECTED' && response.refundStatus === 'NA') {
  2089. document.getElementById("td_refundamount").innerHTML = `Your Booking has been rejected by GCC`;
  2090. document.getElementById("refundamountDetails").style.display = "block";
  2091. document.getElementById("td_bookingStatus").innerHTML = response.bookingStatus;
  2092. document.getElementById("td_refundStatus").innerHTML = response.refundStatus;
  2093. } else if (response.bookingStatus === 'GCC_BLOCKED' && ['WAITING', 'APPROVED', 'INITIATED'].includes(response.refundStatus)) {
  2094. document.getElementById("td_refundamount").innerHTML = `Your booking has been Blocked by GCC. Full amount of ₹ ${parseFloat(response.amountReceived).toFixed(2)} will be refunded shortly`;
  2095. document.getElementById("refundamountDetails").style.display = "block";
  2096. document.getElementById("td_bookingStatus").innerHTML = response.bookingStatus;
  2097. document.getElementById("td_refundStatus").innerHTML = response.refundStatus;
  2098. } else if (response.bookingStatus === 'GCC_BLOCKED' && response.refundStatus === 'COMPLETED') {
  2099. document.getElementById("td_refundamount").innerHTML = `Full amount of ₹${parseFloat(response.amountReceived).toFixed(2)} refunded successfully`;
  2100. document.getElementById("refundamountDetails").style.display = "block";
  2101. document.getElementById("td_bookingStatus").innerHTML = response.bookingStatus;
  2102. document.getElementById("td_refundStatus").innerHTML = response.refundStatus;
  2103. } /*else if(response.scheduleCount === 1){
  2104. document.getElementById("rescheduleDetails").style.display = "block";
  2105. document.getElementById("td_res_start_date").innerHTML = response.startDate;
  2106. document.getElementById("td_res_end_date").innerHTML = response.endDate;
  2107. document.getElementById("td_res_date").innerHTML = response.updatedDate;
  2108. }*/ else {
  2109. document.getElementById("refundamountDetails").style.display = "none";
  2110. }
  2111. // Show the modal
  2112. document.getElementById("modalBookingId").value = bookingId;
  2113. document.getElementById("modalRefId").value = refId;
  2114. $('#showBookingDetails').modal('show');
  2115. },
  2116. error: function () {
  2117. console.error("An error occurred while fetching booking details.");
  2118. }
  2119. });
  2120. }
  2122. function showDamageDetails(data) {
  2123. var damageFieldContainer = $('#damageDetails');
  2124. damageFieldContainer.empty();
  2126. // Create a div for table responsiveness
  2127. var tableResponsiveDiv = $('<div>').addClass('table-responsive').css({
  2128. 'margin-top': '-19px',
  2129. 'margin-left': '19px'
  2130. });
  2131. ;
  2133. // Create table with similar classes and styles to the modal table
  2134. var table = $('<table>').addClass('table table-bordered table-striped').css({
  2135. 'width': '97%',
  2136. 'border-color': 'black',
  2137. 'border-top-color': 'white',
  2138. 'width': ' 730px'
  2139. });
  2140. var thead = $('<thead>').addClass('thead-light');
  2141. var tbody = $('<tbody>');
  2143. // Create Damage Details header row
  2144. var headerRow = $('<tr>').appendTo(thead);
  2145. $('<th>').attr('colspan', '6').text('Damage Details (if any)').css({
  2146. 'padding': '0.45rem 0.45rem',
  2147. 'background-color': 'lightgrey',
  2148. 'font-weight': 'bold',
  2149. 'color': 'black',
  2150. }).appendTo(headerRow);
  2152. // Create table header row
  2153. var columnHeadersRow = $('<tr>').css('background-color', 'white').appendTo(thead);
  2154. $('<th>').text('S.No').css('padding', '0.45rem 0.45rem').appendTo(columnHeadersRow);
  2155. $('<th>').text('Asset Name').css('padding', '0.45rem 0.45rem').appendTo(columnHeadersRow);
  2156. $('<th>').text('Damage Img').css('padding', '0.45rem 0.45rem').appendTo(columnHeadersRow);
  2157. $('<th>').text('Cost').css('padding', '0.45rem 0.45rem').appendTo(columnHeadersRow);
  2158. $('<th>').text('Qty').css('padding', '0.45rem 0.45rem').appendTo(columnHeadersRow);
  2159. $('<th>').text('Amount').css('padding', '0.45rem 0.45rem').appendTo(columnHeadersRow);
  2161. var totalAmount = 0;
  2162. $.each(data.damageList, function (index, detail) {
  2163. var row = $('<tr>').appendTo(tbody);
  2164. $('<td>').text(index + 1).css('padding', '0.45rem 0.45rem').appendTo(row);
  2165. $('<td>').text(detail.assetName).css('padding', '0.45rem 0.45rem').appendTo(row);
  2166. var viewLink = $('<a>').attr('href', 'javascript:void(0)').text('View').on('click', function () {
  2167. showDamageImage(detail.damageImageUrl);
  2168. });
  2169. var assetamt = (detail.assetAmount / detail.quantity).toFixed(2);
  2170. $('<td>').css('padding', '0.45rem 0.45rem').append(viewLink).appendTo(row);
  2171. $('<td>').text(assetamt).css('padding', '0.45rem 0.45rem').appendTo(row);
  2172. $('<td>').text(detail.quantity).css('padding', '0.45rem 0.45rem').appendTo(row);
  2173. var amount = detail.assetAmount;
  2174. totalAmount += amount;
  2175. $('<td>').text(amount.toFixed(2)).css('padding', '0.45rem 0.45rem').appendTo(row);
  2176. $("#td_dam_amt").html(totalAmount.toFixed(2));
  2177. });
  2178. // Add row for total amount
  2179. var totalRow = $('<tr>').appendTo(tbody);
  2180. $('<td>').attr('colspan', '5').text('Total Amount').css('padding', '0.45rem 0.45rem; font-weight: bold; background-color: #f2f2f2').appendTo(totalRow);
  2181. $('<td>').text(totalAmount.toFixed(2)).css('padding', '0.45rem 0.45rem').appendTo(totalRow);
  2183. // Append the table elements to the container div
  2184. table.append(thead, tbody);
  2185. tableResponsiveDiv.append(table);
  2186. damageFieldContainer.append(tableResponsiveDiv);
  2188. var temp_total = parseFloat($("#td_settel_amt").html());
  2189. var settleAmount = temp_total - totalAmount;
  2190. if (settleAmount < 0) {
  2191. var pendingstatus = data.settlement.collectionStatus
  2192. $("#td_settel_amt").html(0.00);
  2193. $("#pendingcolumn").show();
  2194. $("#collectionstatuscolumn").show();
  2195. $('#td_collection_status').html(pendingstatus);
  2196. $("#td_pending_amt").html(Math.abs(settleAmount).toFixed(2));
  2197. $("#td_pending_amt").css("color", "red");
  2198. } else {
  2199. $("#td_settel_amt").html(settleAmount.toFixed(2));
  2200. $("#pendingcolumn").hide();
  2201. $("#collectionstatuscolumn").hide();
  2202. $("#td_settel_amt").css("color", "green"); // Set color to green for positive amounts
  2203. }
  2204. }
  2207. function showDamageImage(damageImageUrl) {
  2208. document.getElementById('filePreview').src = damageImageUrl;
  2209. $('#fileModal').modal('show');
  2210. }
  2212. function showchallonimage(challanImgLink) {
  2213. document.getElementById('filePreview').src = challanImgLink;
  2214. $('#fileModal').modal('show');
  2215. }
  2217. function showReasonDocuments(list) {
  2218. $.ajax({
  2219. type: "GET",
  2220. url: '/communityhall/api/officer/getReasonByName',
  2221. data: {
  2222. 'reasonName': list.reason
  2223. },
  2224. success: function (x) {
  2225. showReasonWithDocument(x, list);
  2226. }
  2227. });
  2228. }
  2230. // Display booking documents
  2231. function showReasonWithDocument(reasonData, list) {
  2232. var reasonDocumentData = reasonData.reasonDocumentMasterList;
  2233. var bookingDocumentsList = list.bookingDocumentsList;
  2235. const reasonFieldsContainer = $('#documents');
  2236. reasonFieldsContainer.empty();
  2238. // Create a responsive table container
  2239. var tableResponsiveDiv = $('<div>').addClass('table-responsive').css({
  2240. 'width': '729px',
  2241. 'border': '1px solid black'
  2242. });
  2244. // Create the table with Bootstrap classes and custom styles
  2245. var table = $('<table>').addClass('table table-bordered table-striped table-vcenter js-dataTable-responsive').css({
  2246. 'width': '100%',
  2247. 'height': 'auto',
  2248. 'border': '1px solid black'
  2249. });
  2251. // Create the table header (thead)
  2252. var thead = $('<thead>').appendTo(table);
  2253. var headerRow = $('<tr>').appendTo(thead);
  2254. $('<th>').attr('colspan', '3').text('Document Details').css({
  2255. 'color': 'black',
  2256. 'background-color': 'lightgrey',
  2257. 'padding': '0.45rem 0.45rem'
  2258. }).appendTo(headerRow);
  2260. // Create header row for columns
  2261. var columnHeadersRow = $('<tr>').appendTo(thead);
  2262. $('<th>').text('S.No').appendTo(columnHeadersRow);
  2263. $('<th>').text('Required Info').appendTo(columnHeadersRow);
  2264. $('<th>').text('Required Documents').appendTo(columnHeadersRow);
  2266. // Create the table body (tbody)
  2267. var tbody = $('<tbody>').appendTo(table);
  2269. // Iterate through the documents list and populate rows
  2270. for (var i = 0; i < bookingDocumentsList.length; i++) {
  2271. (function (index) {
  2272. var row = $('<tr>').appendTo(tbody);
  2273. $('<td>').text(index + 1).appendTo(row);
  2275. // Determine the text content for the second cell
  2276. var name = bookingDocumentsList[index].name ? bookingDocumentsList[index].name : ''; // Empty string if name is null or undefined
  2277. var fieldText = reasonDocumentData[index].fieldName;
  2278. var fullText = name ? fieldText + ': ' + name : fieldText; // Include colon only if name is not empty
  2280. $('<td>').text(fullText).appendTo(row);
  2282. // Create a link to view document image
  2283. var viewLink = $('<a>').attr('href', 'javascript:void(0)').text(reasonDocumentData[index].docFieldName).on('click', function () {
  2284. showDocumentImage(bookingDocumentsList[index].bookingDocUrl);
  2285. });
  2286. $('<td>').append(viewLink).appendTo(row);
  2287. })(i);
  2288. }
  2289. // Append table to the responsive container
  2290. tableResponsiveDiv.append(table);
  2292. // Append table to the container in the DOM
  2293. reasonFieldsContainer.append(tableResponsiveDiv);
  2294. }
  2297. function showDocumentImage(fileURL) {
  2298. openFileModal(fileURL);
  2299. }
  2301. // Event delegation for dynamically added elements
  2302. $(document).on('click', '.view-document', function () {
  2303. const fileURL = $(this).data('url');
  2304. openFileModal(fileURL);
  2305. });
  2307. function openFileModal(fileURL) {
  2308. $('#filePreview').attr('src', fileURL);
  2309. $('#fileModal').modal('show');
  2310. }
  2312. // For OTP input box
  2313. $('.otp-input').on('keyup', function (e) {
  2314. var $this = $(this);
  2315. if ($this.val().length === 1) {
  2316. $this.next('.otp-input').focus();
  2317. }
  2318. if ($this.val().length === 0) {
  2319. $this.prev('.otp-input').focus();
  2320. }
  2321. });
  2323. function cancelBooking(bookingId, mobileNo, bookingType) {
  2324. var mobileNum = mobileNo;
  2325. var bookingId = bookingId;
  2327. // Check if the booking type is OFFLINE
  2328. if (bookingType === "OFFLINE") {
  2329. Swal.fire({
  2330. title: 'Cancellation Not Available',
  2331. text: 'Cancellation is not available for offline bookings.',
  2332. icon: 'error'
  2333. });
  2334. } else {
  2335. Swal.fire({
  2336. title: 'Are you sure?',
  2337. text: 'Once canceled, this action can\'t be undo. Only the deposit Amount will be refunded within 3 to 15 days.',
  2338. icon: 'warning',
  2339. showCancelButton: true,
  2340. confirmButtonColor: '#3085d6',
  2341. cancelButtonColor: '#d33',
  2342. confirmButtonText: 'Yes, cancel it!',
  2343. cancelButtonText: 'Close',
  2344. }).then((result) => {
  2345. if (result.isConfirmed) {
  2346. // If user confirms, show OTP form
  2347. mobileNumberForCancel = mobileNum;
  2348. cancelBookingId = bookingId;
  2349. cancelBookingLogin = true;
  2350. sendOTP(mobileNum);
  2351. }
  2352. });
  2353. }
  2354. }
  2356. function resetRescheduleOTPSection() {
  2357. // Hide OTP section
  2358. var otpSection = document.getElementById("otpSection");
  2359. if (otpSection) {
  2360. otpSection.style.display = "none";
  2361. }
  2363. // Show reschedule button and hide verify button
  2364. var rescheduleBtn = document.getElementById("rescheduleBtn");
  2365. var verifyOtpBtn = document.getElementById("verifyOtpBtn");
  2367. if (rescheduleBtn) {
  2368. rescheduleBtn.style.display = "inline-block";
  2369. }
  2370. if (verifyOtpBtn) {
  2371. verifyOtpBtn.style.display = "none";
  2372. }
  2374. // Clear OTP input fields
  2375. for (let i = 1; i <= 6; i++) {
  2376. var otpField = document.getElementById("otp" + i);
  2377. if (otpField) {
  2378. otpField.value = "";
  2379. }
  2380. }
  2382. // Reset variables
  2383. rescheduleBookingId = null;
  2384. rescheduleStartDate = null;
  2385. rescheduleEndDate = null;
  2386. rescheduleMobileNumber = null;
  2387. rescheduleHallId = null;
  2388. rescheduleStartingSlot = null;
  2389. rescheduleEndingSlot = null;
  2390. rescheduleReason = null;
  2391. }
  2393. function openRescheduleModal(bookingId, startDate, endDate, noOfDays, hallId, startingSlot, endingSlot, reason) {
  2394. // Function to map slot values to their text representation
  2395. function getSlotText(slot) {
  2396. return slot === 1 ? 'Morning' : 'Evening';
  2397. }
  2399. // Populate modal inputs
  2400. const start = new Date(startDate);
  2401. const end = new Date(endDate);
  2402. const timeDiff = end - start;
  2404. // Convert time difference from milliseconds to days
  2405. const daysDiff = Math.ceil(timeDiff / (1000 * 3600 * 24)) + 1;
  2407. // Set values for inputs
  2408. document.getElementById("bookingId").value = bookingId;
  2409. document.getElementById("startDateInput").value = startDate;
  2410. document.getElementById("endDateInput").value = endDate;
  2411. document.getElementById("noOfDaysInput").value = noOfDays;
  2412. document.getElementById("startingSlot").value = String(startingSlot);
  2413. document.getElementById("endingSlot").value = String(endingSlot);
  2414. document.getElementById("endingSlotHidden").value = String(endingSlot);
  2415. document.getElementById("daysDiff").value = daysDiff;
  2417. // Display slot text in the modal
  2418. document.getElementById("startDatetext").value = startDate;
  2419. // document.getElementById("startingSlotText").value = getSlotText(startingSlot);
  2420. // document.getElementById("endingSlotText").value = getSlotText(endingSlot);
  2422. // Store booking details for OTP verification
  2423. rescheduleBookingId = bookingId;
  2424. rescheduleStartDate = startDate;
  2425. rescheduleEndDate = endDate;
  2426. rescheduleHallId = hallId;
  2427. rescheduleStartingSlot = startingSlot;
  2428. rescheduleEndingSlot = endingSlot;
  2429. rescheduleReason = reason;
  2431. // Optionally, fetch and update calendar or availability based on hallId
  2432. getBookingCalendar(hallId, reason);
  2434. // Show the date change modal
  2435. $('#bookingRescheduleModal').modal('show');
  2436. }
  2439. function getBookingCalendar(hall_id, reason) {
  2440. // Make an AJAX call to fetch booking data
  2441. $.ajax({
  2442. type: 'GET',
  2443. url: '/communityhall/user/api/getPastData',
  2444. data: {
  2445. hall_id: hall_id
  2446. },
  2448. success: function (response) {
  2449. window.bookingResponse = {};
  2450. if (response && Array.isArray(response)) {
  2451. $("#startDateInput").datepicker("destroy");
  2452. for (var i = 0; i < response.length; i++) {
  2453. var dateString = datepickerFormat(response[i].bdate);
  2454. window.bookingResponse[dateString] = [response[i].morning_slot, response[i].evening_slot,
  2455. response[i].is_blocked, response[i].booking_status1, response[i].booking_status2];
  2456. }
  2458. initializeDatepickerWithColors(hall_id, reason);
  2459. if (response.length == 0) {
  2460. initializeDatepickerWithColors(hall_id, reason);
  2461. }
  2462. } else {
  2463. console.error('Invalid or empty response data.');
  2464. }
  2465. },
  2466. error: function (xhr, status, error) {
  2467. console.error('Error fetching hall details:', error);
  2468. }
  2469. });
  2470. }
  2472. function initializeDatepickerWithColors(hallId, reason) { // Confirm hallId is passed here
  2473. $("#datepicker-container").datepicker("destroy");
  2474. const serverDate = new Date($("#serverDate").val() + "T00:00:00")
  2475. // console.log(" view history Date:", serverDate);
  2477. const maxDate = new Date(serverDate);
  2478. maxDate.setMonth(maxDate.getMonth() + 6);
  2479. // console.log("View History: "+maxDate);
  2481. $("#startDateInput,#datepicker-container").datepicker({
  2482. dateFormat: "yy-mm-dd",
  2483. minDate: serverDate,
  2484. maxDate: maxDate,
  2485. beforeShowDay: function (eDate) {
  2487. const dateString = $.datepicker.formatDate("yy-mm-dd", eDate);
  2488. const bookingStatus = window.bookingResponse[dateString] || {};
  2490. // const currentDate = new Date();
  2491. serverDate.setHours(0, 0, 0, 0); // Normalize current date to midnight
  2492. eDate.setHours(0, 0, 0, 0); // Normalize selected date to midnight
  2494. // Logic for other dates
  2495. if (eDate < serverDate) {
  2496. return [false, "highlight-disabled", "Slot not Available"];
  2497. }
  2499. const isToday = eDate.getTime() === serverDate.getTime();
  2500. const currentHour = new Date().getHours();
  2501. const isBefore6AM = currentHour < 6;
  2502. const isAfter2PM = currentHour >= 14;
  2504. // Block 3-day logic for specific event types
  2505. // const today = new Date();
  2506. const blockedDate = new Date(serverDate);
  2507. blockedDate.setDate(serverDate.getDate() + 2);
  2509. const isThreeDayBlock = ["Commercial", "State Govt Event", "Central Govt Event"].includes(reason);
  2510. if (eDate <= blockedDate && isThreeDayBlock) {
  2511. return [false, "highlight-disabled", "Blocked due to event type"];
  2512. }
  2514. // Logic for currentdate
  2515. if (isToday) {
  2516. if (isBefore6AM) {
  2517. // Before 6 AM: Allow full-day booking or adjust based on booking status
  2518. return handleBookingStatus(bookingStatus, "Full Day Available");
  2519. } else if (isAfter2PM) {
  2520. // After 2 PM: Block all bookings
  2521. return handleAfter2PM(bookingStatus);
  2522. } else {
  2523. // Between 6 AM and 2 PM: Check status and disable morning slots
  2524. return handleMorningSlots(bookingStatus, isToday);
  2525. }
  2526. }
  2528. return handleBookingStatus(bookingStatus, "Slot Available");
  2529. },
  2530. });
  2532. $("#startDateInput").on("change", function () {
  2533. var selectedDate = $(this).val();
  2534. // var noOfDays = document.getElementById('noOfDaysInput').value;
  2535. var startingSlot = document.getElementById("startingSlot").value;
  2536. var endingSlot = document.getElementById("endingSlotHidden").value;
  2537. var noofdays = document.getElementById("noOfDaysInput").value;
  2538. updateEndDate(selectedDate, noofdays, startingSlot, endingSlot);
  2539. });
  2541. // ── Custom tooltip for calendar cells (handles pointer-events:none on .disabled) ──
  2542. // The <td> itself still receives mouse events even when its child has pointer-events:none.
  2543. // We read the title attribute that jQuery UI datepicker sets via beforeShowDay's 3rd return value.
  2544. if (!document.getElementById('dp-tooltip')) {
  2545. $('body').append('<div id="dp-tooltip"></div>');
  2546. }
  2547. $("#datepicker-container")
  2548. .off('mouseenter.dptt mouseleave.dptt mousemove.dptt', 'td[title]')
  2549. .on('mouseenter.dptt', 'td[title]', function (e) {
  2550. var tip = $(this).attr('title');
  2551. if (!tip) return;
  2552. $('#dp-tooltip').text(tip).css({
  2553. left: (e.clientX + 12) + 'px',
  2554. top: (e.clientY - 30) + 'px'
  2555. }).show();
  2556. })
  2557. .on('mousemove.dptt', 'td[title]', function (e) {
  2558. $('#dp-tooltip').css({
  2559. left: (e.clientX + 12) + 'px',
  2560. top: (e.clientY - 30) + 'px'
  2561. });
  2562. })
  2563. .on('mouseleave.dptt', 'td[title]', function () {
  2564. $('#dp-tooltip').hide();
  2565. });
  2567. }
  2569. function handleBookingStatus(bookingStatus, defaultMessage) {
  2570. if (bookingStatus[2] && bookingStatus[0] && !bookingStatus[1]) {
  2571. return [false, "highlight-yellow disabled", "GCC Blocked"];
  2572. } else if (bookingStatus[2] && bookingStatus[1] && !bookingStatus[0]) {
  2573. return [false, "highlight-violet disabled", "GCC Blocked"];
  2574. } else if (bookingStatus[2] && bookingStatus[1] && bookingStatus[0] && bookingStatus[3] != 'GCC_BLOCKED' && bookingStatus[4] != 'GCC_BLOCKED') {
  2575. return [false, "highlight-pink disabled", "GCC Blocked"];
  2576. } else if (bookingStatus[2] && bookingStatus[1] && bookingStatus[0] && bookingStatus[3] == 'GCC_BLOCKED' && bookingStatus[4] == 'GCC_BLOCKED') {
  2577. return [false, "highlight-blue disabled", "GCC Blocked"];
  2578. } else if (bookingStatus[2]) {
  2579. return [false, "highlight-blue disabled", "GCC Blocked"];
  2580. } else if (bookingStatus[0] && bookingStatus[1]) {
  2581. return [true, "highlight-pink disabled", "Slot Occupied"];
  2582. } else if (bookingStatus[0] && !bookingStatus[1]) {
  2583. return [true, "highlight-yellow", "Evening Slot Available"];
  2584. } else if (!bookingStatus[0] && bookingStatus[1]) {
  2585. return [true, "highlight-violet", "Only Morning Slot Available"];
  2586. }
  2587. return [true, "highlight-greens", defaultMessage];
  2588. }
  2590. // Helper function: Handles logic after 2 PM
  2591. function handleAfter2PM(bookingStatus) {
  2592. if (bookingStatus[2] && bookingStatus[0] && !bookingStatus[1]) {
  2593. return [true, "highlight-yellow disabled", "GCC Blocked"];
  2594. } else if (bookingStatus[2] && bookingStatus[1] && !bookingStatus[0]) {
  2595. return [true, "highlight-violet disabled", "GCC Blocked"];
  2596. } else if (bookingStatus[2] && bookingStatus[1] && bookingStatus[0] && bookingStatus[3] != 'GCC_BLOCKED' && bookingStatus[4] != 'GCC_BLOCKED') {
  2597. return [true, "highlight-pink disabled", "GCC Blocked"];
  2598. } else if (bookingStatus[2] && bookingStatus[1] && bookingStatus[0] && bookingStatus[3] == 'GCC_BLOCKED' && bookingStatus[4] == 'GCC_BLOCKED') {
  2599. return [true, "highlight-blue disabled", "GCC Blocked"];
  2600. } else if (bookingStatus[2]) {
  2601. return [true, "highlight-blue disabled", "GCC Blocked"];
  2602. } else if (bookingStatus[0] || bookingStatus[1]) {
  2603. return [true, "highlight-pink disabled", "Slot Occupied"];
  2604. }
  2605. return [false, "highlight-disabled", "Not Allowed to Book"];
  2606. }
  2608. // Helper function: Handles morning slots between 6 AM and 2 PM
  2609. function handleMorningSlots(bookingStatus, isToday) {
  2610. console.log("isToday....." + isToday);
  2611. if (bookingStatus[2] && bookingStatus[0] && !bookingStatus[1]) {
  2612. return [true, "highlight-yellow disabled", "GCC Blocked"];
  2613. } else if (bookingStatus[2] && bookingStatus[1] && !bookingStatus[0]) {
  2614. if (isToday) {
  2615. return [false, "highlight-disabled", "GCC Blocked"];
  2616. }
  2617. return [true, "highlight-violet disabled", "GCC Blocked"];
  2618. } else if (bookingStatus[2] && bookingStatus[1] && bookingStatus[0] && bookingStatus[3] != 'GCC_BLOCKED' && bookingStatus[4] != 'GCC_BLOCKED') {
  2619. return [true, "highlight-pink disabled", "GCC Blocked"];
  2620. } else if (bookingStatus[2] && bookingStatus[1] && bookingStatus[0] && bookingStatus[3] == 'GCC_BLOCKED' && bookingStatus[4] == 'GCC_BLOCKED') {
  2621. return [true, "highlight-blue disabled", "GCC Blocked"];
  2622. } else if (bookingStatus[2]) {
  2623. return [true, "highlight-blue disabled", "GCC Blocked"];
  2624. } else if (bookingStatus[0] && bookingStatus[1]) {
  2625. return [true, "highlight-pink disabled", "Slot Occupied"];
  2626. } else if (bookingStatus[0] && !bookingStatus[1]) {
  2627. return [true, "highlight-yellow", "Evening Slot Available"];
  2628. } else if (!bookingStatus[0] && bookingStatus[1]) {
  2629. return [false, "highlight-disabled", "Slot Occupied"];
  2630. }
  2631. return [true, "highlight-yellow", "Evening Slot Available"];
  2632. }
  2634. // Helper: returns true if the given date string is GCC-blocked
  2635. function isGCCBlockedDate(dateStr) {
  2636. var status = window.bookingResponse[dateStr] || [];
  2637. return (status[2] == true || status[2] == 1 ||
  2638. status[3] === 'GCC_BLOCKED' ||
  2639. status[4] === 'GCC_BLOCKED');
  2640. }
  2642. function updateEndDate(startDate, noofdays, startingSlot, endingSlot) {
  2643. if (startDate && noofdays !== undefined) {
  2644. var start = new Date(startDate);
  2645. var startFormatted = start.toISOString().split('T')[0];
  2646. var bookingStatus = window.bookingResponse[startFormatted] || [false, false];
  2647. var morningAvailable = !bookingStatus[0]; // false means available
  2648. var eveningAvailable = !bookingStatus[1]; // false means available
  2649. var isgccBlock = bookingStatus[2];
  2650. var bookingStatus1 = bookingStatus[3];
  2651. var bookingStatus2 = bookingStatus[4];
  2652. var endDate;
  2653. var isValid = true; // Flag to determine if all slots are available
  2655. // Convert noofdays to a number for accurate calculations
  2656. noofdays = parseFloat(noofdays);
  2658. // --- GCC Block checkpoint ---
  2659. // Block reschedule if the start date is GCC-blocked via any of the three status flags
  2660. if (isgccBlock == true || isgccBlock == 1 ||
  2661. bookingStatus1 === 'GCC_BLOCKED' ||
  2662. bookingStatus2 === 'GCC_BLOCKED') {
  2663. Swal.fire({
  2664. title: 'Date Not Available',
  2665. text: 'The selected start date is blocked by GCC. Please choose a different date.',
  2666. icon: 'warning',
  2667. confirmButtonText: 'OK'
  2668. });
  2669. document.getElementById('endDateInput').value = "";
  2670. return;
  2671. }
  2672. // --- End GCC Block checkpoint ---
  2674. // Handle slot availability and combinations
  2675. if (startingSlot === "2" && endingSlot === "2") { // Evening to Evening
  2676. //console.log("Handling Evening to Evening slot.");
  2677. if (noofdays === 0.5) {
  2678. if (eveningAvailable) {
  2679. endDate = new Date(start);
  2680. endDate.setDate(start.getDate() + Math.ceil(noofdays) - 1);
  2681. endDate = endDate.toISOString().split('T')[0];
  2682. document.getElementById('endDateInput').value = endDate;
  2683. //console.log("End Date (Evening to Evening):", endDate);
  2684. } else {
  2685. Swal.fire({
  2686. title: 'Evening Slot Not Available',
  2687. text: 'The evening slot is not available for the selected date range.',
  2688. icon: 'warning',
  2689. confirmButtonText: 'OK'
  2690. });
  2691. document.getElementById('endDateInput').value = "";
  2692. //console.log("Evening slot not available for", noofdays, "days.");
  2693. }
  2694. } else if (noofdays === 1.5) {
  2695. // Special handling for 2 days
  2696. let endDateCandidate = new Date(start);
  2697. endDateCandidate.setDate(start.getDate() + 1);
  2698. let endDateFormattedCandidate = endDateCandidate.toISOString().split('T')[0];
  2699. let endDateStatusCandidate = window.bookingResponse[endDateFormattedCandidate] || [false, false];
  2700. let morningAvailableOnEndDate = !endDateStatusCandidate[0]; // false means available
  2701. let eveningAvailableOnEndDate = !endDateStatusCandidate[1]; // false means available
  2703. if (eveningAvailable && morningAvailableOnEndDate && eveningAvailableOnEndDate) {
  2704. endDate = endDateCandidate.toISOString().split('T')[0];
  2705. // --- GCC Block check for end date ---
  2706. if (isGCCBlockedDate(endDate)) {
  2707. Swal.fire({
  2708. title: 'End Date Not Available',
  2709. text: 'The end date is blocked by GCC. Please choose a different start date.',
  2710. icon: 'warning',
  2711. confirmButtonText: 'OK'
  2712. });
  2713. document.getElementById('endDateInput').value = "";
  2714. } else {
  2715. document.getElementById('endDateInput').value = endDate;
  2716. }
  2717. //console.log("End Date (Morning to Evening with 2 days):", endDate);
  2718. } else {
  2719. Swal.fire({
  2720. title: 'Slot Not Available',
  2721. text: 'The Morning slots are not available for the selected date range.',
  2722. icon: 'warning',
  2723. confirmButtonText: 'OK'
  2724. });
  2725. document.getElementById('endDateInput').value = "";
  2726. //console.log("Morning or Evening slot not available for 2 days.");
  2727. }
  2728. } else {
  2729. //console.log("Unsupported duration for Evening to Evening slot.");
  2730. Swal.fire({
  2731. title: 'Invalid Selection',
  2732. text: 'The selected duration for the evening slot is not supported.',
  2733. icon: 'error',
  2734. confirmButtonText: 'OK'
  2735. });
  2736. document.getElementById('endDateInput').value = "";
  2737. }
  2738. } else if (startingSlot === "1" && endingSlot === "1") { // Morning to Morning
  2739. //console.log("Handling Morning to Morning slot.");
  2740. if (noofdays === 0.5) {
  2741. if (morningAvailable) {
  2742. endDate = new Date(start);
  2743. endDate.setDate(start.getDate() + Math.ceil(noofdays) - 1);
  2744. endDate = endDate.toISOString().split('T')[0];
  2745. document.getElementById('endDateInput').value = endDate;
  2746. //console.log("End Date (morning to morning):", endDate);
  2747. } else {
  2748. Swal.fire({
  2749. title: 'Morning Slot Not Available',
  2750. text: 'The Morning slot is not available for the selected date range.',
  2751. icon: 'warning',
  2752. confirmButtonText: 'OK'
  2753. });
  2754. document.getElementById('endDateInput').value = "";
  2755. //console.log("Evening slot not available for", noofdays, "days.");
  2756. }
  2757. } else if (noofdays === 1.5) {
  2758. // Special handling for 2 days
  2759. let endDateCandidate = new Date(start);
  2760. endDateCandidate.setDate(start.getDate() + 1);
  2761. let endDateFormattedCandidate = endDateCandidate.toISOString().split('T')[0];
  2762. let endDateStatusCandidate = window.bookingResponse[endDateFormattedCandidate] || [false, false];
  2763. let morningAvailableOnEndDate = !endDateStatusCandidate[0]; // false means available
  2764. let eveningAvailableOnEndDate = !endDateStatusCandidate[1]; // false means available
  2766. if (morningAvailable && eveningAvailable && morningAvailableOnEndDate) {
  2767. endDate = endDateCandidate.toISOString().split('T')[0];
  2768. // --- GCC Block check for end date ---
  2769. if (isGCCBlockedDate(endDate)) {
  2770. Swal.fire({
  2771. title: 'End Date Not Available',
  2772. text: 'The end date is blocked by GCC. Please choose a different start date.',
  2773. icon: 'warning',
  2774. confirmButtonText: 'OK'
  2775. });
  2776. document.getElementById('endDateInput').value = "";
  2777. } else {
  2778. document.getElementById('endDateInput').value = endDate;
  2779. }
  2780. //console.log("End Date (Morning to Evening with 2 days):", endDate);
  2781. } else {
  2782. Swal.fire({
  2783. title: 'Slot Not Available',
  2784. text: 'The evening slots are not available for the selected date range.',
  2785. icon: 'warning',
  2786. confirmButtonText: 'OK'
  2787. });
  2788. document.getElementById('endDateInput').value = "";
  2789. //console.log("Morning or Evening slot not available for 2 days.");
  2790. }
  2791. } else {
  2792. //console.log("Unsupported duration for Morning to Morning slot.");
  2793. Swal.fire({
  2794. title: 'Invalid Selection',
  2795. text: 'The selected duration for the morning slot is not supported.',
  2796. icon: 'error',
  2797. confirmButtonText: 'OK'
  2798. });
  2799. document.getElementById('endDateInput').value = "";
  2800. }
  2801. } else if (startingSlot === "1" && endingSlot === "2") { // Morning to Evening
  2802. //console.log("Handling Morning to Evening slot.");
  2803. if (noofdays === 1) {
  2804. if (morningAvailable && eveningAvailable) {
  2805. endDate = new Date(start);
  2806. endDate.setDate(start.getDate() + Math.ceil(noofdays) - 1);
  2807. endDate = endDate.toISOString().split('T')[0];
  2808. document.getElementById('endDateInput').value = endDate;
  2809. //console.log("End Date (Morning to Evening):", endDate);
  2810. } else {
  2811. Swal.fire({
  2812. title: ' Slot Not Available',
  2813. text: 'The Selected slot is not available for the selected date range.',
  2814. icon: 'warning',
  2815. confirmButtonText: 'OK'
  2816. });
  2817. document.getElementById('endDateInput').value = "";
  2818. //console.log("Evening slot not available for", noofdays, "days.");
  2819. }
  2820. } else if (noofdays === 2) {
  2821. // Special handling for 2 days
  2822. let endDateCandidate = new Date(start);
  2823. endDateCandidate.setDate(start.getDate() + 1);
  2824. let endDateFormattedCandidate = endDateCandidate.toISOString().split('T')[0];
  2825. let endDateStatusCandidate = window.bookingResponse[endDateFormattedCandidate] || [false, false];
  2826. let morningAvailableOnEndDate = !endDateStatusCandidate[0]; // false means available
  2827. let eveningAvailableOnEndDate = !endDateStatusCandidate[1]; // false means available
  2829. if (morningAvailable && eveningAvailable && morningAvailableOnEndDate && eveningAvailableOnEndDate) {
  2830. endDate = endDateCandidate.toISOString().split('T')[0];
  2831. // --- GCC Block check for end date ---
  2832. if (isGCCBlockedDate(endDate)) {
  2833. Swal.fire({
  2834. title: 'End Date Not Available',
  2835. text: 'The end date is blocked by GCC. Please choose a different start date.',
  2836. icon: 'warning',
  2837. confirmButtonText: 'OK'
  2838. });
  2839. document.getElementById('endDateInput').value = "";
  2840. } else {
  2841. document.getElementById('endDateInput').value = endDate;
  2842. }
  2843. //console.log("End Date (Morning to Evening with 2 days):", endDate);
  2844. } else {
  2845. Swal.fire({
  2846. title: 'Slot Not Available',
  2847. text: 'The morning and/or evening slots are not available for the selected date range.',
  2848. icon: 'warning',
  2849. confirmButtonText: 'OK'
  2850. });
  2851. document.getElementById('endDateInput').value = "";
  2852. //console.log("Morning or Evening slot not available for 2 days.");
  2853. }
  2854. } else {
  2855. //console.log("Unsupported duration for Morning to Evening slot.");
  2856. Swal.fire({
  2857. title: 'Invalid Selection',
  2858. text: 'The selected duration for the morning to evening slot is not supported.',
  2859. icon: 'error',
  2860. confirmButtonText: 'OK'
  2861. });
  2862. document.getElementById('endDateInput').value = "";
  2863. }
  2864. } else if (startingSlot === "2" && endingSlot === "1") { // Evening to Morning
  2865. //console.log("Handling Evening to Morning slot.");
  2866. if (noofdays === 1) {
  2867. if (eveningAvailable) { // Check if evening slot is available
  2868. let nextDay = new Date(start);
  2869. nextDay.setDate(start.getDate() + 1);
  2870. let nextDayFormatted = nextDay.toISOString().split('T')[0];
  2871. let nextDayStatus = window.bookingResponse[nextDayFormatted] || [false, false];
  2872. let nextDayMorningAvailable = !nextDayStatus[0]; // false means available
  2874. if (nextDayMorningAvailable) {
  2875. endDate = nextDay.toISOString().split('T')[0];
  2876. // --- GCC Block check for end date ---
  2877. if (isGCCBlockedDate(endDate)) {
  2878. Swal.fire({
  2879. title: 'End Date Not Available',
  2880. text: 'The end date is blocked by GCC. Please choose a different start date.',
  2881. icon: 'warning',
  2882. confirmButtonText: 'OK'
  2883. });
  2884. document.getElementById('endDateInput').value = "";
  2885. } else {
  2886. document.getElementById('endDateInput').value = endDate;
  2887. }
  2888. //console.log("End Date (Evening to Morning):", endDate);
  2889. } else {
  2890. Swal.fire({
  2891. title: 'Morning Slot Not Available',
  2892. text: 'The morning slot is not available for the next day.',
  2893. icon: 'warning',
  2894. confirmButtonText: 'OK'
  2895. });
  2896. document.getElementById('endDateInput').value = "";
  2897. //console.log("Morning slot not available for the next day.");
  2898. }
  2899. } else {
  2900. Swal.fire({
  2901. title: 'Evening Slot Not Available',
  2902. text: 'The evening slot is not available for the selected date.',
  2903. icon: 'warning',
  2904. confirmButtonText: 'OK'
  2905. });
  2906. document.getElementById('endDateInput').value = "";
  2907. //console.log("Evening slot not available for", startDate);
  2908. }
  2909. } else {
  2910. //console.log("Unsupported duration for Evening to Morning slot.");
  2911. Swal.fire({
  2912. title: 'Invalid Selection',
  2913. text: 'The selected duration for the evening to morning slot is not supported.',
  2914. icon: 'error',
  2915. confirmButtonText: 'OK'
  2916. });
  2917. document.getElementById('endDateInput').value = "";
  2918. }
  2919. } else {
  2920. //console.log("Unsupported slot combination or duration.");
  2921. Swal.fire({
  2922. title: 'Invalid Slot Combination',
  2923. text: 'The selected slot combination or duration is not supported.',
  2924. icon: 'error',
  2925. confirmButtonText: 'OK'
  2926. });
  2927. document.getElementById('endDateInput').value = "";
  2928. }
  2929. } else {
  2930. //console.log("Start Date or Number of Days not provided.");
  2931. Swal.fire({
  2932. title: 'Invalid Input',
  2933. text: 'Please provide a valid start date and number of days.',
  2934. icon: 'error',
  2935. confirmButtonText: 'OK'
  2936. });
  2937. document.getElementById('endDateInput').value = "";
  2938. }
  2939. }
  2941. function datepickerFormat(dateString) {
  2942. var dateObject = new Date(dateString);
  2943. var year = dateObject.getFullYear();
  2944. var month = (dateObject.getMonth() + 1).toString().padStart(2, "0");
  2945. var day = dateObject.getDate().toString().padStart(2, "0");
  2946. return `${year}-${month}-${day}`;
  2947. }
  2949. function printTables() {
  2950. // Get the printable content
  2951. var printableContent = document.getElementById('printableContent').innerHTML;
  2952. // Open a print window
  2953. var printWindow = window.open('', '', 'height=400,width=600');
  2954. // Write the printable content to the print window
  2955. printWindow.document.write('<html><head><title>Print</title></head><body>' + printableContent + '</body></html>');
  2957. // Close the print window after printing
  2958. printWindow.document.close();
  2959. printWindow.print();
  2960. printWindow.close();
  2961. }
  2963. function Reschedule() {
  2964. // --- Slot availability check for today's date ---
  2965. var startDate = document.getElementById("startDateInput").value;
  2966. var startingSlot = document.getElementById("startingSlot").value;
  2967. var endingSlot = document.getElementById("endingSlotHidden").value;
  2968. var todayDateStr = $("#serverDate").val();
  2969. var currentHour = new Date().getHours();
  2971. if (startDate === todayDateStr) {
  2972. // Morning slot (1) is NOT available after 6 AM
  2973. if (startingSlot === "1" && currentHour >= 6) {
  2974. Swal.fire({
  2975. icon: 'warning',
  2976. title: 'Morning Slot Not Available',
  2977. text: 'The Morning slot is not available for today as it is already past 6:00 AM. Please select a different date.',
  2978. showConfirmButton: true
  2979. });
  2980. return;
  2981. }
  2982. // Evening/Afternoon slot (2) is NOT available after 2 PM (14:00)
  2983. if (endingSlot === "2" && currentHour >= 14) {
  2984. Swal.fire({
  2985. icon: 'warning',
  2986. title: 'Afternoon Slot Not Available',
  2987. text: 'The Afternoon/Evening slot is not available for today as it is already past 2:00 PM. Please select a different date.',
  2988. showConfirmButton: true
  2989. });
  2990. return;
  2991. }
  2992. // After 2 PM: no slots available at all for today
  2993. if (currentHour >= 14) {
  2994. Swal.fire({
  2995. icon: 'warning',
  2996. title: 'No Slots Available',
  2997. text: 'No slots are available for today as it is already past 2:00 PM. Please select a future date.',
  2998. showConfirmButton: true
  2999. });
  3000. return;
  3001. }
  3002. }
  3003. // --- End slot availability check ---
  3005. // Get mobile number and show OTP modal for verification
  3006. $.ajax({
  3007. type: "GET",
  3008. url: '/communityhall/user/api/viewAllBookingDetails',
  3009. data: { bookingId: rescheduleBookingId },
  3010. success: function (response) {
  3011. rescheduleMobileNumber = response.users.mobileNo;
  3013. // Show mobile number in OTP modal
  3014. document.getElementById("rescheduleMobileTxt").textContent = rescheduleMobileNumber;
  3016. // Clear any previous OTP errors
  3017. document.getElementById("rescheduleOtpError").textContent = "";
  3019. // Clear OTP inputs
  3020. for (let i = 1; i <= 5; i++) {
  3021. document.getElementById("rescheduleOtp" + i).value = "";
  3022. }
  3024. // Close date change modal and show OTP modal
  3025. $('#bookingRescheduleModal').modal('hide');
  3026. $('#rescheduleOtpModal').modal('show');
  3028. // Send OTP immediately
  3029. sendRescheduleOTP(rescheduleMobileNumber);
  3030. },
  3031. error: function () {
  3032. Swal.fire({
  3033. icon: 'error',
  3034. title: 'Error',
  3035. text: 'Failed to get booking details. Please try again.',
  3036. showConfirmButton: true
  3037. });
  3038. }
  3039. });
  3040. }
  3042. var rescheduleTimer = null;
  3043. var RESCHEDULE_TIME = 60;
  3045. function sendRescheduleOTP(mobileNumber) {
  3046. $.ajax({
  3047. type: "GET",
  3048. url: "/communityhall/user/api/sendOTP",
  3049. data: {
  3050. mobileNo: mobileNumber,
  3051. purpose: "reschedule"
  3052. },
  3053. success: function (response) {
  3054. // Start countdown timer
  3055. startRescheduleCountdown();
  3056. },
  3057. error: function () {
  3058. Swal.fire({
  3059. icon: 'error',
  3060. title: 'Error',
  3061. text: 'Failed to send OTP. Please try again.',
  3062. showConfirmButton: true
  3063. });
  3064. }
  3065. });
  3066. }
  3068. // function startRescheduleCountdown() {
  3069. // var resendTimeout;
  3070. // var resendLink = $("#rescheduleResendLink");
  3071. // $("#rescheduleResendLink").html('<a href="#" id="rescheduleResendLink" class="text-info" onclick="return resendRescheduleOTP();">Resend OTP</a>');
  3072. // var countdown = $("#rescheduleCountdown");
  3074. // function startCountdown() {
  3075. // var timeleft = 60;
  3076. // countdown.text(timeleft);
  3078. // resendTimeout = setInterval(function () {
  3079. // timeleft--;
  3080. // countdown.text(timeleft);
  3082. // if (timeleft <= 0) {
  3083. // clearInterval(resendTimeout);
  3084. // $("#rescheduleResendLink").html('<a href="#" id="rescheduleResendLink" class="text-info" onclick="return sendRescheduleOTP(' + rescheduleMobileNumber + ');">Resend OTP</a>');
  3085. // }
  3086. // }, 1000);
  3087. // }
  3089. // startCountdown();
  3090. // }
  3092. function startRescheduleCountdown() {
  3094. clearInterval(rescheduleTimer); // prevent multiple timers
  3096. var timeLeft = RESCHEDULE_TIME;
  3098. $("#rescheduleResendText").text("Please wait..");
  3099. $("#rescheduleCountdown").text(timeLeft);
  3101. rescheduleTimer = setInterval(function () {
  3103. timeLeft--;
  3104. $("#rescheduleCountdown").text(timeLeft);
  3106. if (timeLeft <= 0) {
  3107. clearInterval(rescheduleTimer);
  3109. $("#rescheduleResendText").html(
  3110. '<a href="#" class="text-info" onclick="sendRescheduleOTP(' + rescheduleMobileNumber + '); return false;">Resend OTP</a>'
  3111. );
  3112. $("#rescheduleCountdown").text('');
  3113. }
  3115. }, 1000);
  3116. }
  3119. function resendRescheduleOTP() {
  3120. if (rescheduleMobileNumber) {
  3121. sendRescheduleOTP(rescheduleMobileNumber);
  3122. // Restart countdown timer after resending OTP
  3123. startRescheduleCountdown();
  3124. }
  3125. }
  3127. function verifyRescheduleOtp() {
  3128. // Get all the input fields with class `otp-input`
  3129. var otpInputs = $('.otp-input');
  3131. // Get the OTP value as a string
  3132. var otpValue = '';
  3133. otpInputs.each(function () {
  3134. otpValue += $(this).val();
  3135. });
  3137. if (otpValue.length !== 5) {
  3138. document.getElementById("rescheduleOtpError").textContent = "Please enter complete OTP";
  3139. return false;
  3140. }
  3142. // Verify OTP
  3143. $.ajax({
  3144. type: "GET",
  3145. url: "/communityhall/user/api/verifyofficialOTP",
  3146. data: {
  3147. otp: otpValue
  3148. },
  3149. dataType: 'text',
  3150. success: function (response) {
  3151. if (response.trim() === "Success") {
  3152. // OTP verified successfully, close OTP modal and proceed with reschedule
  3153. $('#rescheduleOtpModal').modal('hide');
  3154. validateDatesAndReschedule();
  3155. } else {
  3156. document.getElementById("rescheduleOtpError").textContent = "OTP is Incorrect!!!";
  3157. // Clear OTP inputs
  3158. for (let i = 1; i <= 5; i++) {
  3159. document.getElementById("rescheduleOtp" + i).value = "";
  3160. }
  3161. }
  3162. },
  3163. error: function () {
  3164. document.getElementById("rescheduleOtpError").textContent = "Error verifying OTP. Please try again.";
  3165. }
  3166. });
  3168. return false;
  3169. }
  3175. function proceedWithReschedule() {
  3176. // Debug: Log the data being sent
  3177. console.log('Reschedule data:', {
  3178. bookingId: rescheduleBookingId,
  3179. startDate: rescheduleStartDate,
  3180. endDate: rescheduleEndDate,
  3181. startingSlot: rescheduleStartingSlot,
  3182. endingSlot: rescheduleEndingSlot
  3183. });
  3185. $.ajax({
  3186. type: "POST",
  3187. url: "/communityhall/user/api/reschedule-dates",
  3188. data: {
  3189. bookingId: rescheduleBookingId,
  3190. startDate: rescheduleStartDate,
  3191. endDate: rescheduleEndDate,
  3192. startingSlot: rescheduleStartingSlot,
  3193. endingSlot: rescheduleEndingSlot
  3194. },
  3195. success: function (response) {
  3196. Swal.fire({
  3197. icon: 'success',
  3198. title: 'Success',
  3199. text: 'Booking rescheduled successfully!',
  3200. showConfirmButton: true
  3201. }).then((result) => {
  3202. if (result.isConfirmed) {
  3203. // Close modal and reload page
  3204. $('#bookingRescheduleModal').modal('hide');
  3205. location.reload();
  3206. }
  3207. });
  3208. },
  3209. error: function (xhr, status, error) {
  3210. console.error('Reschedule API Error:', {
  3211. status: xhr.status,
  3212. statusText: xhr.statusText,
  3213. responseText: xhr.responseText,
  3214. error: error
  3215. });
  3217. let errorMessage = 'Failed to reschedule booking. Please try again.';
  3219. if (xhr.responseText) {
  3220. try {
  3221. const errorData = JSON.parse(xhr.responseText);
  3222. errorMessage = errorData.message || errorData.error || errorMessage;
  3223. } catch (e) {
  3224. errorMessage = xhr.responseText || errorMessage;
  3225. }
  3226. }
  3228. Swal.fire({
  3229. icon: 'error',
  3230. title: 'Error',
  3231. text: errorMessage,
  3232. showConfirmButton: true
  3233. });
  3234. }
  3235. });
  3236. }
  3238. function validateDatesAndReschedule() {
  3239. // Retrieve values from modal inputs
  3241. var startDate = document.getElementById("startDateInput").value;
  3242. var endDate = document.getElementById("endDateInput").value;
  3243. var originalStartDate = document.getElementById("startDatetext").value;
  3244. var startingSlot = document.getElementById("startingSlot").value;
  3245. // var endingSlot = document.getElementById("endingSlot").value;
  3246. var endingSlot = document.getElementById("endingSlotHidden").value;
  3248. // Get today's date from server
  3249. var todayDateStr = $("#serverDate").val();
  3250. var currentHour = new Date().getHours();
  3252. // Debug: Log the retrieved dates
  3253. console.log('Retrieved dates:', {
  3254. startDate: startDate,
  3255. endDate: endDate,
  3256. originalStartDate: originalStartDate,
  3257. startingSlot: startingSlot,
  3258. endingSlot: endingSlot,
  3259. todayDateStr: todayDateStr,
  3260. currentHour: currentHour
  3261. });
  3263. // Check if the rescheduled start date is the same as the original booked start date
  3264. // if (startDate === originalStartDate) {
  3265. // Swal.fire({
  3266. // icon: 'warning',
  3267. // title: 'Warning',
  3268. // text: 'Your Rescheduled Start Date is the same as Your booking Start Date. Please change the date.',
  3269. // showConfirmButton: true
  3270. // });
  3271. // return;
  3272. // }
  3273. if (!endDate) {
  3274. Swal.fire({
  3275. icon: 'error',
  3276. title: 'Error',
  3277. text: 'End Date is Empty! Please check your Start Date',
  3278. showConfirmButton: true
  3279. });
  3280. return;
  3281. }
  3283. // --- Slot availability check for today's date ---
  3284. // If the new start date is today, validate slot against current time
  3285. if (startDate === todayDateStr) {
  3286. // Morning slot (1) is NOT available after 6 AM
  3287. if (startingSlot === "1" && currentHour >= 6) {
  3288. Swal.fire({
  3289. icon: 'warning',
  3290. title: 'Morning Slot Not Available',
  3291. text: 'The Morning slot is not available for today as it is already past 6:00 AM. Please select a different date or slot.',
  3292. showConfirmButton: true
  3293. });
  3294. return;
  3295. }
  3296. // Evening/Afternoon slot (2) is NOT available after 2 PM (14:00)
  3297. if (endingSlot === "2" && currentHour >= 14) {
  3298. Swal.fire({
  3299. icon: 'warning',
  3300. title: 'Afternoon Slot Not Available',
  3301. text: 'The Afternoon/Evening slot is not available for today as it is already past 2:00 PM. Please select a different date.',
  3302. showConfirmButton: true
  3303. });
  3304. return;
  3305. }
  3306. // After 2 PM: no slots available at all for today
  3307. if (currentHour >= 14) {
  3308. Swal.fire({
  3309. icon: 'warning',
  3310. title: 'No Slots Available',
  3311. text: 'No slots are available for today as it is already past 2:00 PM. Please select a future date.',
  3312. showConfirmButton: true
  3313. });
  3314. return;
  3315. }
  3316. }
  3317. // --- End slot availability check ---
  3319. // Store the validated dates
  3320. rescheduleStartDate = startDate;
  3321. rescheduleEndDate = endDate;
  3322. rescheduleStartingSlot = document.getElementById('startingSlot').value;
  3323. rescheduleEndingSlot = document.getElementById('endingSlotHidden').value;
  3325. // Debug: Log the final dates being sent
  3326. console.log('Final reschedule dates:', {
  3327. startDate: rescheduleStartDate,
  3328. endDate: rescheduleEndDate,
  3329. startingSlot: rescheduleStartingSlot,
  3330. endingSlot: rescheduleEndingSlot,
  3331. bookingId: rescheduleBookingId
  3332. });
  3333. proceedWithReschedule();
  3334. }
  3336. $(document).ready(function () {
  3337. // DataTables buttons configuration
  3338. var buttons = [
  3339. {
  3340. extend: 'pageLength',
  3341. className: 'btn btn-primary'
  3342. }
  3343. ];
  3344. $('#simpletable').DataTable({
  3345. dom: 'Bftip',
  3346. columnDefs: [
  3347. { targets: 'no-sort', orderable: false }
  3348. ],
  3349. lengthMenu: [
  3350. [5, 10, 20, 50, -1],
  3351. ['5 rows', '10 rows', '20 rows', '50 rows', 'Show all']
  3352. ],
  3353. scrollY: '50vh',
  3354. fixedColumns: {
  3355. left: 1,
  3356. right: 1
  3357. },
  3358. buttons: [buttons],
  3359. responsive: true,
  3360. searching: true, // Enable search
  3361. select: false,
  3362. processing: false,
  3363. });
  3366. $('#searchInput').on('keyup', function () {
  3367. dataTable.search(this.value).draw();
  3368. });
  3369. });
  3370. $(document).on('change', '.nocfile', function () {
  3371. validateFile(this);
  3372. });
  3374. function transactionHistory(userId) {
  3375. $.ajax({
  3376. type: "GET",
  3377. url: '/communityhall/user/api/getTransactionDetails',
  3378. data: { 'userId': userId },
  3379. success: function (data) {
  3380. // console.log("Full response:", data);
  3381. // console.log("Refund Details:", data.refundDetails);
  3384. const transactions = data.transactions || [];
  3385. const refundDetails = data.refundDetails || [];
  3387. populateTransactionTable(transactions);
  3388. populateRefundDetailsTable(refundDetails);
  3390. $('#transactionHistoryModal').modal('show'); // Show the modal
  3391. },
  3392. error: function (error) {
  3393. console.error("Error fetching transaction details", error);
  3394. }
  3395. });
  3396. }
  3398. function populateTransactionTable(transactions) {
  3399. const tableBody = $('#transactionTable tbody');
  3400. tableBody.empty(); // Clear any existing rows
  3402. transactions.forEach((transaction, index) => {
  3403. const paymentStatus = (transaction.statusCode === "0300" && transaction.response?.includes("success"))
  3404. ? "Success"
  3405. : "Payment Failed";
  3407. const row = `
  3408. <tr>
  3409. <td>${index + 1}</td>
  3410. <td>${transaction.bookingId}</td>
  3411. <td>${transaction.amount || '-'}</td>
  3412. <td>${transaction.date || '-'}</td>
  3413. <td>${transaction.txansactionId || '-'}</td>
  3414. <td>${paymentStatus}</td>
  3415. </tr>
  3416. `;
  3417. tableBody.append(row); // Append the row to the table body
  3418. });
  3419. }
  3421. function populateRefundDetailsTable(refundDetails) {
  3422. const refundTable = $('#refunddetails');
  3423. const tableBody = $('#refunddetailsTable tbody');
  3424. tableBody.empty(); // Clear any existing rows
  3426. if (refundDetails.length > 0) {
  3427. refundTable.show(); // Show the refund details table
  3429. refundDetails.forEach((refund, index) => {
  3430. const row = `
  3431. <tr>
  3432. <td>${index + 1}</td>
  3433. <td>${refund.bookingId}</td>
  3434. <td>${refund.amount}</td>
  3435. <td>${refund.date}</td>
  3436. <td>${refund.txansactionId}</td>
  3437. <td>${refund.refundAmount}</td>
  3438. </tr>
  3439. `;
  3440. tableBody.append(row);
  3441. });
  3442. } else {
  3443. refundTable.hide(); // Hide the refund details table
  3444. }
  3445. }
  3448. // Toggle Chat Box
  3449. function toggleChat() {
  3450. const chatBox = document.getElementById('chat-box');
  3451. chatBox.style.display = (chatBox.style.display === 'block') ? 'none' : 'block';
  3452. }
  3454. // Send Message
  3455. function sendMessage() {
  3456. const userInput = document.getElementById('userInput');
  3457. const message = userInput.value.trim();
  3459. if (message) {
  3460. // Create message element
  3461. const chatBody = document.getElementById('chat-body');
  3462. const userMessage = document.createElement('div');
  3463. userMessage.className = 'user-message';
  3464. userMessage.textContent = message;
  3466. chatBody.appendChild(userMessage);
  3467. chatBody.scrollTop = chatBody.scrollHeight; // Auto-scroll to bottom
  3469. // Send message to the server (Spring Boot API)
  3470. fetch('/communityhall/admin/api/send', {
  3471. method: 'POST',
  3472. headers: {
  3473. 'Content-Type': 'application/json',
  3474. },
  3475. body: JSON.stringify({ message }),
  3476. })
  3477. .then(response => response.json())
  3478. .then(data => {
  3479. // Add response message to chat
  3480. const responseMessage = document.createElement('div');
  3481. responseMessage.className = 'bot-message';
  3482. responseMessage.textContent = data.response;
  3484. chatBody.appendChild(responseMessage);
  3485. chatBody.scrollTop = chatBody.scrollHeight;
  3486. });
  3488. userInput.value = ''; // Clear input field
  3489. }
  3490. }
  3492. // ── Slot helper ──────────────────────────────────────────────────────
  3493. // Ending slot is deterministic: given (startSlot + noOfDays) there is
  3494. // exactly one valid ending slot. The user can only change Starting Slot;
  3495. // Ending Slot auto-fixes based on this table:
  3496. //
  3497. // noOfDays | start=1(Morning) → end | start=2(Afternoon) → end
  3498. // ---------|------------------------|-------------------------
  3499. // 0.5 | 1 (same slot, half-day) | 2 (same slot, half-day)
  3500. // 1 | 2 (6AM→10PM, full day) | 1 (2PM→next day 2PM)
  3501. // 1.5 | 1 (6AM→next day 2PM) | 2 (2PM→next day 10PM)
  3502. // 2 | 2 (6AM→day+1 10PM) | ❌ not allowed
  3504. function computeEndingSlot(startSlot, noOfDays) {
  3505. startSlot = String(startSlot);
  3506. noOfDays = parseFloat(noOfDays);
  3507. if (noOfDays === 0.5) return startSlot; // same slot, half-day
  3508. if (noOfDays === 1) return startSlot === "1" ? "2" : "1"; // flip: full-day
  3509. if (noOfDays === 1.5) return startSlot; // same slot, 1.5 days
  3510. if (noOfDays === 2) return startSlot === "1" ? "2" : null; // only morning valid for 2-day
  3511. return null;
  3512. }
  3514. // When user changes Starting Slot → auto-fix Ending Slot, re-validate end date
  3515. document.getElementById("startingSlot").addEventListener("change", function () {
  3516. var startSlot = this.value;
  3517. var noOfDays = parseFloat(document.getElementById("noOfDaysInput").value);
  3518. var endSlot = computeEndingSlot(startSlot, noOfDays);
  3520. // Guard: Afternoon start is not valid for 2-day booking
  3521. if (endSlot === null) {
  3522. Swal.fire({
  3523. icon: 'warning',
  3524. title: 'Slot Not Allowed',
  3525. text: 'Afternoon start is not supported for a ' + noOfDays + '-day booking. Reverting to the original slot.',
  3526. showConfirmButton: true
  3527. });
  3528. this.value = String(rescheduleStartingSlot);
  3529. return;
  3530. }
  3532. // Auto-fix the (disabled) ending slot display and its hidden mirror
  3533. document.getElementById("endingSlot").value = endSlot;
  3534. document.getElementById("endingSlotHidden").value = endSlot;
  3536. // Clear the computed end date — user must re-pick or it will re-compute
  3537. document.getElementById("endDateInput").value = "";
  3539. // If a start date is already selected, re-compute end date immediately
  3540. var startDate = document.getElementById("startDateInput").value;
  3541. if (startDate) {
  3542. updateEndDate(startDate, noOfDays, startSlot, endSlot);
  3543. }
  3544. });
  3546. // OTP input navigation for reschedule modal
  3547. $('.otp-input').on('keyup', function (e) {
  3548. var $this = $(this);
  3549. if ($this.val().length === 1) {
  3550. $this.next('.otp-input').focus();
  3551. }
  3552. if ($this.val().length === 0) {
  3553. $this.prev('.otp-input').focus();
  3554. }
  3555. });
  3557. // Clear OTP inputs when OTP modal is shown
  3558. $('#rescheduleOtpModal').on('shown.bs.modal', function () {
  3559. $('.otp-input').val('');
  3560. $('#rescheduleOtpError').text('');
  3561. });
  3563. </script>
  3565. </div>
  3566. </div>
  3567. </div>
  3568. </body>
  3570. </html>