"Just Do It" override
hammer a square peg into a round hole.
BRM has many many features, but perhaps the core 2 features are:
- keep track of all your bikes' reservations to avoid double bookings. So each bike has its own calendar and BRM respects it.
- tracking each reservation around its lifecycle.
BUT - feature no1 sometimes means you can't book a bike when you think perhaps you should be able to.
In other words, life/reality gets in the way...
Let's say you have 2 bookings starting today:
- John is renting: M mountain bike @10:30am
- Dave is renting: M mountain bike @11:00am
Dave arrives first and takes bike M1, but sadly the operator makes a mistake and tells BRM about the wrong bike - M2.
Then John turns up and you wheel out M2 to give him. You know you're going to give him M2 because you have it in your hand, but BRM says NO! Because it says it is already checked out due to the operator's previous mistake, and rule no1 applies - avoiding double-bookings.
"Just Do It" is an override feature. It lets you do something which normally would not be allowed.
Previously you'd have to perhaps tell BRM you have him M1 (even though you knew that was wrong!).
But, as we know, two wrongs do not make a right!
Just Do It is very powerful
But with power comes responsibility and danger!
It is only a last resort - and you should follow up to find out why BRM said no.
So now you can invoke the 'just do it' (JDI) operation to 'force it in anyway'. So at least now you've only made 1 error, it doesn't have to cascade into an ever-increasing number of errors.
In this example I'm trying to deliberately make a double-booking for the same bike on the same date&time to demonstrate JDI. BRM correctly detects that you can't normally do this - and tells you exactly why.
But it does also present the JDI button if you really need to do this.
Ideally, you should go back to the original reservation and fix it...
Meanwhile, BRM will warn you that night when it does the overnight checker that 2 bikes were checked out at the same time.
Please note that there are really quite a few scenarios when this can occur:
- swapping a bike
- adding a bike
- simply creating a reservation
- changing reservation dates (JDI not currently available)
- allocating a bike in 'barcode mode'
- you have broken bikes and so you're actually over-capacity for that product line
- GBAL booking - and subsequent allocate
- assigning product within a package (JDI not currently available)
over time 'Just do it' will evolve into universally available functionality, and with clear indications in affected reservations.
Please Note! - use the feature only when absolutely essential
This feature comes with a major health warning! Clearly allowing users to break rule no1 is highly dangerous and can lead to double bookings. For this reason, all reservations that have ever had a JDI applied to it will be permanently stamped with JDI.
Here you'll see the next step from the story above - I went ahead and made the reservation:
Inventory underpinning each reservation