Public Bus Transportation

Public Bus Transportation ginstr app

Page describes how to setup initial environment to use "publicBusTransportation" ginstr app.

ROLES

following roles should be created on SSO main account and assigned to subaccounts

bus driver

Bus Drivers (busDrivers) = RU
Bus Drivers Logs (busDriverWorkLogs) = CRU
Buses (buses) = RU
Bus Stops (busStops) = R
Bus Stops Per Route (busStopsPerRoute) = R
MOBICard statuses (MOBICardStatuses) = R
Operators (operators) = R
Passengers (passengers) = R
Routes (routes) = R
Special Incidents Passenger (specialIncidentsPassengers) = C
Trips (trips) = CRU

controller

Bus Controller Checks (ticketControllerBusChecks) = CR
Bus Drivers (busDrivers) = R
Buses (buses) = R
Bus Stops (busStops) = R
Bus Stops Per Route (busStopsPerRoute) = R
MOBICard statuses (MOBICardStatuses) = R
Operators (operators) = R
Passengers (passengers) = RU
Pax Controller Checks (ticketControllerPassengerChecks) = CRU
Suspensions (suspensionTypes) = R
Ticket Controllers (controllers) = R

retailer

Actual Top-Ups (topUps) = C
Fare basis (fareBasis) = R
GSM Networks (GSMNetworks) = R
MOBICard statuses (MOBICardStatuses) = R
Passengers (passengers) = CRU
Ticket Retailers (retailers) = R

MOBI staff

all tables full CRUD

OBLIGATORY ENTRIES IN TABLES

This app should work only on "English" at time of writing this. Since we do not have "localized enums" it's necessary to rely on english "fixed value" data to determine some logical states which are required by BL (Business Logic).

Following tables require following data:

TABLE fareBasis (rows to add)

fareBasis_name	fareBasis_comments
Regular	any comment

TABLE MOBICardStatuses (rows to add)

MOBICardStatus_name	MOBICardStatus_validity
Active	true
Inactive	false
Suspended	false

TABLE busDrivers:
busDriver_ssoUsername - has to contain at least one driver entry which has column filled with email address of subaccount which has assigned role of "driver"

TABLE controllers:
controller_ssoUsername - has to contain at least one driver entry which has column filled with email address of subaccount which has assigned role of "controller"

TABLE retailers:
retailer_ssoUsername - has to contain at least one driver entry which has column filled with email address of subaccount which has assigned role of "retailer"

In addition following tables will need to be filled with some data in backend for not blocked workflows on ginstr app: GSMNetworks, Operators, Suspension types, Routes, Bus stops, Bus stops per route all other tables data can be entered via ginstr app