charter NVO app / "office" hierarchy use to delimit contact choice in charter app segments

charter NVO app / "office" hierarchy use to delimit contact choice in charter app segments

By selecting a customer, can we use a category?
(why? Every charter has only a few customers, it is easier to let the driver choose at 2 or 3 customers then the whole reation database.  

(it is important for invoicing to do this correct)

We will fix.
But this will be done by using Units level.
We can’t use category, as this is to specific from customer to customer.

-->

Have now created this 4 units.
Drivers could go into this department unit “Drivers”
(I have moved the username “sb-app” into this)

 mceclip0.png

And customer, load, unload here on office level, under the “Drivers” unit.

mceclip1.png

Right now the username “sb-app” wont be able to see any contacts, as we have moved it from the company unit, where all the contacts is placed right now. To change this, move contacts from the company unit to Driver department og office units under Driver department.

Also important to know, when the driver creates new customer/load/unload contacts, it will go into the department unit, the same level as the driver.

And to understand, there is no logic between choose of customer, load and unload in the app and the unit name. Is just a level logic, to filter contacts away from the driver not to use.

-------------------

Correct, you have moved the admin-account away from the Company unit. I have moved it back. This user MUST be in the Company unit.

In the Department unit “Drivers” I see you have placed the drivers, including username “sb-app”. That’s correct.

Contacts placed in one of these Office units (screendump), contacts from Department unit “Drivers” will be able to see. It’s not a require to put them there. You could also put them on the same level as the Drivers itself, the Department unit. New contacts created from the App, will also go into there, as we place them in the same level as the login.

mceclip0.png

So feel free to create/delete all Office (or not use them) as you like and name them what you like, only require is that the Office unit must be under the Department unit “Drivers”. So delete Unload office and rename Load office to Load/Unload or whatever, this will also work.

 

    • Related Articles

    • charter NVO app - start finish km's per ride

      I think the total of the kilometers per ride is very nice, but can we also note the start and finish of the kilometers? --> Not possible as we use odometer for start and end and multiple vehicles is able to drive a Dispatch, with different odometers. ...

    • charter app NVO - temperatur logic

      All products placed in a product-group with ID ending “/!” is now required for enter a value (temp). Example “app/inventory/fruit/!” Products in a group without “/!” will still be able to enter a value, but not required. Label for the field to enter ...

    • charter NVO app - mileage logic

      add some logic to the mileage? the final mileage can never be less than the startmileage and perhaps not deviate more than 5000 km --> As we enter Start / End Km each vehicle, we will display the Start Km when enter End Km and ensure it’s not posible ...

    • charter NVO app - Translation remarks

      Translation is done. But I see it’s not possible to choose Nederlands, sorry. This will be fixed. Default will be English, as this is a shared login page. But after you choose ex. Nederlands, it will remember the chosen language in 7 days.

    • charter NVO app - temp registration HACCP

      for the purposes of the HACCP rules, foodstuffs must always be temperature-tested and therefore we must register a temperature (in the case of no and yes). so actually there must be a Temp. field where you can register your temperature, what you have ...