IT Glitch when searching and or cancelling reservations

[DeeDibble]

Has anyone noticed that the website isn’t cancelling points and returning them when cancelling more than 15 days out? This happened on my account the 1st week in January and now happening when I tried to cancel something I have scheduled in February. I have talked to Owner Care and they made sure I got points back for the cancelled January reservation and now it’s an issue for the February reservation. This newest Website is a pathetic system - anyone heard when the IT Department is going to fix this? I just have lost any trust in the system

 

[Sandi Bo]

Oh wow, I'll have to check more carefully. I haven't noticed any missing. Thanks for posting.

Sent from my SM-N960U1 using Tapatalk

 

[weleftmn]

I recently cancelled a reservation and the points were returned in the amount of time I expect. It isn't immediate usually give it a bit.

 

[SNA27]

I canceled a February 7 reservation on Jan 23 and got my points back.
After Cancellation, you get an option to go back to the reservation or points history. Did you go to points history? And there was no credit of points?
Don't go by the balance in the use-year shown to you by the frontend, it lags behind the backend which is the keeper of records. That balance doesn't get refreshed in real-time.
But, from what I have figured out so far of this 'mysterious' system, the point history is a real-time look into the backend.

 

[pagosajim]

I canceled a February 7 reservation on Jan 23 and got my points back.
After Cancellation, you get an option to go back to the reservation or points history. Did you go to points history? And there was no credit of points?
Don't go by the balance in the use-year shown to you by the frontend, it lags behind the backend which is the keeper of records. That balance doesn't get refreshed in real-time.
But, from what I have figured out so far of this 'mysterious' system, the point history is a real-time look into the backend.

It would appear to me that the points ARE returned in real time, it's just the page that you use to display them doesn't update right away or during your current session.

Many times I will use the Points Calculator on that very page to confirm the cancelled reservation points are back in the proper use year. Alternatively, logging out and then back in again has always shown the correct total in for me.

 

[SNA27]

The page that displays points history is a real-time JOURNAL from the backend.
Use-year buckets are front-end LEDGERS that are not updated in real-time.
JOURNAL is the independent primary source and LEDGERS are dependent, secondary accumulations of JOURNAL transactions.

Anyone who understands Double-Entry Book-Keeping from the pre-computer era can relate to the fact that JOURNAL is the key and LEDGERS can always be recreated from the JOURNAL.

Btw, doesn't 'logging off and logging back on' sound like mumbo-jumbo or voodoo magic?

 

[pagosajim]

The page that displays points history is a real-time JOURNAL from the backend.
Use-year buckets are front-end LEDGERS that are not updated in real-time.
JOURNAL is the independent primary source and LEDGERS are dependent, secondary accumulations of JOURNAL transactions.

Not really seeing how the accounting analogy is germane to the issue. It's fundamentally MVC (model-view-controller) web design.

The "use year buckets" are simply a page object that they have CHOSEN to not update as the transactions occur. Just as your "ledger" is updated, so could your "journal" on that very same page.

 

[liquidmas]

I cancelled a reservation Monday and immediately booked a different reservation. Cancelled points were immediately available to use. They did not show up on My Points page on site but system recognized they were available to use to book a reservation.

Mike

 

[SNA27]

Not really seeing how the accounting analogy is germane to the issue. It's fundamentally MVC (model-view-controller) web design.

The "use year buckets" are simply a page object that they have CHOSEN to not update as the transactions occur. Just as your "ledger" is updated, so could your "journal" on that very same page.

Those page objects have a database source in the front end. I am saying that the frontend database is not updated in real-time. But the journal is kept in the backend and it's always up to date. This is what I have observed from outside looking at the behavior of the system without the benefit of a peek at their design. I could be wrong.

 

[HitchHiker71]

It would appear to me that the points ARE returned in real time, it's just the page that you use to display them doesn't update right away or during your current session.

Many times I will use the Points Calculator on that very page to confirm the cancelled reservation points are back in the proper use year. Alternatively, logging out and then back in again has always shown the correct total in for me.

In other words - it's at least in part a browser caching issue - which has nothing to do with either the front or back end design of the website itself. Different people use different browser cache and cookie control settings within their personal browsers - as well as different browsers (IE/Edge/Firefox/Chrome/Safari/etc.) which makes for different user experiences that are dependent upon settings outside of the website design itself. This fact is why it's often futile to attempt to "test" scenarios via web forums like this - since it's practically impossible to ensure an apples to apples comparison when the people participating in the test scenarios are all using different browsers with different security/cache settings.

 

[pagosajim]

Those page objects have a database source in the front end. I am saying that the frontend database is not updated in real-time. But the journal is kept in the backend and it's always up to date. This is what I have observed from outside looking at the behavior of the system without the benefit of a peek at their design. I could be wrong.

There's no "front end" database. All the data is stored on the "backend" (model). The "front end" (view) is where that data is presented/viewed/manipulated (what the user interacts with). Middleware software/services (controller) handle the exchange of information between the frontend and backend.

 

[SNA27]

@pagosajim

My expertise is in the backend, database, supply chain, etc. I don't have web development skills but I do have access to an expert in my son. I am learning from him how to decipher what's transpiring on the web page.

My deduction that there must be a front-end database to support the query and reservations is based on my observation of the delay in some accumulators showing correct numbers, while transactions appear to be shown in real-time. I have also worked on systems where a secondary DB is created to support query functions to take the load off of the backend DB. But, as I said, I could be wrong. As wrong as the 5 blind men trying to describe an elephant by touch!

You obviously know more about the web side of the system. I would love to learn more and continue this in a private conversation.

 

[nkldavy]

I log out and then back in. Correct point count then shows.