Roxyfire
Is butter a carb?
- Joined
- Jul 1, 2015
- Messages
- 2,989
I think someone already said the system didn't differentiate between the tickets at the time the FPs were booked. That's why it allowed the FPs to be booked. Now it does differentiate, but the FPs were already in there. Now it just seems to know something shouldn't be in there, but since it was probably the old coding that allowed it, the new coding doesn't automatically pick up what the issue is.
At this point I don't think the Whys matter. It is what it is... Ugh, I hate that saying. This is the first time in my life that I used it. It really seems to apply here. LOL.
Correct, the system is not smart enough to know your intent. Way back when, in high school, during Computing Concepts, our teacher always told us "The computer is not smart, it only knows what you've told it." So, for those not lucky enough to have that wisdom imparted on them, I'm reminding folks even though we have lots of predictive analytics, big data, and so on, this seems to be fairly simple. It sees a 6 day ticket, and 7 days worth of fastpasses.
I suspect the software process around reserving, maintaining, and redeeming FP+ are operating separately. There's something there allowing the special event ticket to book them but it prevents users (some but not all) from maintaining them after a certain point. Therefore when this process is working, it's not "arbitrary" at all. It just sees 6+1, from our example earlier. It automatically alerts the user account flagged that the +1, or in our scenario earlier the last day of FP+, that those FP+ will be removed. It does not know you intend to use the party ticket. All it knows is the classifcation of tickets allowed to keep FP+.
Some of this could be due to bringing the processes more in line, getting them integrated, or as some say, talking to one another. I know nothing of their set up so these are all just guesses. I'm somewhat familiar with multi-platform process integration and can imagine how it's supposed to be set up from the technical standpoint.