iOS QuickBooker for EMT

TABLE OF CONTENTS

• Pre-Requisite
• Step 1: Create and share specific Hourline Views
• Step 2: Toolbox Configurations
• How does the app look like?
• How does it look in the timelines?

Pre-Requisite

• Requires EMT license (contact sales@farmerswife.com)

Step 1: Create and share specific Hourline Views

• Create and save an Hourline View called “QuickBooker” with objects you wish to allow quick-book on. Do not make it a shared view.

• Share the view in Users web profile “Shared Hourline Views”

• Create and save an Hourline View called “DayPlan” 
  • Choose to add new grouping from Category "Users"
  • This usually contains the staff you need to see and their bookings for the day. The view is structured in the same way as the "Day Plan" that you can run from the Hourline Menu.

• Share in Users web profile “Day Plan Hourline View”

Step 2: Toolbox Configurations

• In Toolbox > Settings > Booking Defaults, create a new Global Status called “QuickBooker” 
  

  
  

  

Note! If you are using the Setting in Toolbox > Setting > Server Setup > Add Object Class .... then the User will be able to book the "Pure" Class Object through the QuickBooker view in iOS!

How does the app look like?

Once the above configuration is in place, the Users will see 2 additional “Tabs” In the Events view:  Day Plan and Quick Booker How to quick book: Click the green BOOK X button to make a quick booking on the Object.  Select time in and out.  Enter a (not mandatory) Note. Good to know! An Object can be booked with overlapping an existing Object > no conflict warning but Booking is set to preliminary, still with Global Status: QuickBooker If there’s a Booking already for an Object, the “Book” button is “grey” but you can still book it. Releasing the Object will result in the deletion of the Booking in farmerswife.

What happens next?

• The Booking will be linked to the first project that the user is booked on that day. 
• If there’s no Project Booking found for the User a Task is created for the booked equipment.
• The Booking is added to a Binder "QuickBooker" in the Project or Binder of the first booking of the Users belongs to.

How does it look in the timelines?

• For quick identification the Booking is added to a Binder = QuickBooker
• Booking Name = QuickBooker
• Global Booking Status = QuickBooker (if previously configured!)

If you do not want for the Users to delete OTHER Bookings than their own:

There's a variable you can configure in the server.cfg:

QUICKBOOKER_ONLY_USER_CAN_REMOVE 

if == 1 Only User who booked in QuickBooker can release their respective event

if == 0 A user can release any Booking in QuickBooker view