Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Training 2022 Linux team/
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training session Tetra team on Safeexpress OBPASS Punjab Noida understanding. Dated 28 Nov 2022 - Tetra Support Staff - Biswajit Banerjee== {{#ev:youtube|izpDL7shJmU|640}} '''Video summary:''' "Training session Tetra team on Safeexpress OBPASS Punjab Noida understanding" -- covers two separate, unrelated projects. First, SafeExpress: a ticket-management LAMP application with a frontend where users log in and generate/view support tickets, and a backend built on a UPI-style internal API for the ticket workflow -- support ownership sits mainly with a colleague (Rakesh) who has the deepest platform knowledge and direct customer contact, so calls on this platform are infrequent and get routed to him. A real past incident is recalled: outbound notification email hit Microsoft 365's default outbound-sending cap (1000 messages/day per account), causing many customer notification emails ("your ticket has been generated") to fail to send during high volume -- resolved by working with the client to raise that limit and tuning based on what the mail logs showed. Second and larger: the OBPASS (Online Building Permission/Approval System) platforms for Punjab and Noida/West Bengal -- a government building-permit approval workflow where an application (e.g. for a house/building in Patiala) routes automatically through the relevant approving authority (e.g. fire department) for review/approval, with multiple government bodies plugged into the same automated routing system. Explains the vendor split: Tetra built the integration/architecture and the overall system routing, while a separate company, Vinjas, built the actual "scrutiny engine" (the core rules/validation logic that checks submitted applications) which plugs into Tetra's architecture. Clarifies scope explicitly: Tetra does NOT manage the underlying infrastructure for this platform (Windows-based) -- support is reactive only, triggered by escalations that come in via a WhatsApp group shared with the client and a partner company (Medha) that also has visibility into both the Punjab and Noida deployments. The application layer is PHP/LAMP-based, built by Tetra's PHP team, with per-client PHP version and module customization handled case-by-case depending on what the original application build required (e.g. serving PHP 7.2 to match what a given deployment was built against, since installing modules independently for a mismatched PHP version won't work). Closes with an open Q&A, noting light attendance (only two trainees present) and encouraging questions be raised immediately rather than saved for later.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)