From wiki.ginstr.com
Jump to: navigation, search
(OBLIGATORY ENTRIES IN TABLES)
Line 59: Line 59:
 
Following tables require following data:
 
Following tables require following data:
  
<code>fareBasis: fareBasis_name, fareBasis_comments <br>
+
<code>TABLE fareBasis: fareBasis_name, fareBasis_comments <br>
 
fareBasis: "Regular", any comment
 
fareBasis: "Regular", any comment
  
MOBICardStatuses: MOBICardStatus_name, MOBICardStatus_validity <br>
+
TABLE MOBICardStatuses: MOBICardStatus_name, MOBICardStatus_validity <br>
MOBICardStatuses: Active, true <br>
+
TABLE MOBICardStatuses: Active, true <br>
MOBICardStatuses: Inactive, false <br>
+
TABLE MOBICardStatuses: Inactive, false <br>
MOBICardStatuses: Suspended, false<br><br>
+
TABLE MOBICardStatuses: Suspended, false<br><br>
 
</code>
 
</code>
 
<code>
 
<code>
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"<br>
+
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"<br>
  
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"<br>
+
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"<br>
  
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"<br>
+
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"<br>
 
</code>
 
</code>

Revision as of 13:41, 15 August 2016


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 and assigned to subaccounts

bus driver

Bus Drivers = RU
Bus Drivers Logs = CRU
Buses = RU
Bus Stops = R
Bus Stops Per Route = R
MOBICard statuses = R
Operators = R
Passengers = R
Routes = R
Special Incidents Passenger = C
Trips = CRU


controller

Bus Controller Checks = CR
Bus Drivers = R
Buses = R
Bus Stops = R
Bus Stops Per Route = R
MOBICard statuses = R
Operators = R
Passengers = RU
Pax Controller Checks = CRU
Suspensions = R
Ticket Controllers = R


retailer

Actual Top-Ups = C
Fare basis = R
GSM Networks = R
MOBICard statuses = R
Passengers = CRU
Ticket 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: fareBasis_name, fareBasis_comments
fareBasis: "Regular", any comment

TABLE MOBICardStatuses: MOBICardStatus_name, MOBICardStatus_validity
TABLE MOBICardStatuses: Active, true
TABLE MOBICardStatuses: Inactive, false
TABLE MOBICardStatuses: 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"