From wiki.ginstr.com
Jump to: navigation, search
(OBLIGATORY ENTRIES IN TABLES)
m
Line 3: Line 3:
 
<div style="float:right; clear:both; margin-left:0.5em;">__TOC__</div>
 
<div style="float:right; clear:both; margin-left:0.5em;">__TOC__</div>
 
<span STYLE="font-size: xx-large">Public Bus Transportation ginstr app</span>
 
<span STYLE="font-size: xx-large">Public Bus Transportation ginstr app</span>
[[Category:Sidebar]]
 
  
Page describes how to setup initial environment to use "publicBusTransportation" ginstr app.
+
This page describes how to setup initial environment to use "publicBusTransportation" ginstr app.
  
= ROLES =
+
=Roles=
 
following roles should be created on SSO main account and assigned to subaccounts
 
following roles should be created on SSO main account and assigned to subaccounts
== bus driver ==
+
==bus driver==
  
 
Bus Drivers (busDrivers) = RU <br>
 
Bus Drivers (busDrivers) = RU <br>
Line 23: Line 22:
 
Trips (trips) = CRU
 
Trips (trips) = CRU
  
== controller ==
+
==controller==
  
 
Bus Controller Checks (ticketControllerBusChecks) = CR <br>
 
Bus Controller Checks (ticketControllerBusChecks) = CR <br>
Line 37: Line 36:
 
Ticket Controllers (controllers) = R
 
Ticket Controllers (controllers) = R
  
 
+
==retailer==
== retailer ==
 
  
 
Actual Top-Ups (topUps) = C <br>
 
Actual Top-Ups (topUps) = C <br>
Line 47: Line 45:
 
Ticket Retailers (retailers) = R
 
Ticket Retailers (retailers) = R
  
 
+
==MOBI staff==
== MOBI staff ==
 
 
all tables full CRUD
 
all tables full CRUD
  
  
= OBLIGATORY ENTRIES IN TABLES =
+
=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).
+
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:
 
Following tables require following data:
  
TABLE fareBasis (rows to add)
+
;TABLE <code>fareBasis</code> (rows to add)
  
 
{| class="wikitable sortable" style="font-size: 85%; text-align: left;"
 
{| class="wikitable sortable" style="font-size: 85%; text-align: left;"
Line 69: Line 66:
 
|}
 
|}
  
TABLE MOBICardStatuses (rows to add)
+
;TABLE <code>MOBICardStatuses</code> (rows to add)
  
 
{| class="wikitable sortable" style="font-size: 85%; text-align: left;"
 
{| class="wikitable sortable" style="font-size: 85%; text-align: left;"
Line 86: Line 83:
 
|}
 
|}
  
 +
;TABLE <code>busDrivers</code>:<code>busDriver_ssoUsername</code> - must contain at least one driver entry which has column filled with email address of subaccount which has assigned role of "driver"
  
TABLE busDrivers:<br>
+
;TABLE <code>controllers</code>:<code>controller_ssoUsername</code> - must to contain at least one driver entry which has column filled with email address of subaccount which has assigned role of "controller"</code>
<code> 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" </code>
 
  
TABLE controllers:<br>
+
;TABLE <code>retailers</code>:<code>retailer_ssoUsername</code> - must to contain at least one driver entry which has column filled with email address of subaccount which has assigned role of "retailer"</code>
<code> 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"</code>
 
  
TABLE retailers:<br>  
+
In addition, the following tables will need to be filled with some data in backend for not blocked workflows on ginstr app:
<code>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"</code>
+
*<code>GSMNetworks</code>
 +
*<code>Operators</code>
 +
*<code>Suspension types</code>
 +
*<code>Routes</code>
 +
*<code>Bus stops</code>
 +
*<code>Bus stops per route</code>
  
In addition following tables will need to be filled with some data in backend for not blocked workflows on ginstr app:
+
:All other tables data can be entered via ginstr app
<code>GSMNetworks, Operators, Suspension types, Routes, Bus stops, Bus stops per route</code> all other tables data can be entered via ginstr app
 

Revision as of 16:34, 16 August 2016


Public Bus Transportation ginstr app

This 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 - must 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 - must 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 - must to contain at least one driver entry which has column filled with email address of subaccount which has assigned role of "retailer"

In addition, the 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