Chapter 1. Setting the Stage
This project was an internal helpdesk modernization initiative at Alfamart. In this phase, the work focused on rebuilding the Security Level or Hak Level module from the legacy Oracle Form environment into a web-based system using Flask, while preserving the original business behavior and improving maintainability for future development.
This work was delivered in collaboration with IT Back Office Development Team.
Chapter 2. Carrying the Work
Responsibilities in this project included System Analysis, Flowchart Design, Front-end Development, Back-end Development, Controller and DAO Development, and SQL Query Development.
Chapter 3. What Changed
This project phase demonstrated how a legacy enterprise helpdesk module could be translated into a web-based workflow without losing its core operational logic. The result was a more maintainable and collaborative development structure, supported by cleaner interface planning, Flask-based back-end logic, and a clearer separation between view, controller, DAO, and query handling.
Chapter 4. The Problem and the Response
Problem
The existing internal helpdesk application still relied on Oracle Form, which made the system less flexible for interface improvements, collaborative development, and long-term modernization. The module needed to be migrated to the web so internal users could work with a more structured, user-friendly, and maintainable system without changing the core operational flow.
Solution
The solution was to rebuild the module as a Flask-based web application while preserving the operational rules that internal users already relied on. My contribution focused on helping translate the legacy module into a more maintainable structure through flow design, interface rebuilding, and system-side implementation support.
Chapter 5. How It Was Built
The Security Level or Hak Level module was used to manage user access information within the company. Users could view records directly and perform create and update actions through the web interface. Compared to the legacy version, the web implementation kept the same functional purpose while improving the layout and making the table structure more aligned with user needs.
Implementation Flow: Flask back-end logic is implemented to support reading records, creating new access entries, and updating existing records. Controllers, DAO structure, and SQL queries are used to connect the interface with PostgreSQL data handling in a more maintainable way. The module is refined with supporting features such as search, code cleanup, and iterative bug fixing during development.
Implementation details included Legacy module migration from Oracle Form to Flask web application, Flowchart-based UI planning before implementation, User interface development with Bootstrap, Back-end service development using Python Flask, Database and query handling with PostgreSQL, and Search feature, bug fixing, and code refinement during iteration.
Some screens and implementation details have been intentionally generalized because this was an internal enterprise project.
Chapter 6. Application Flow
Primary Flow: The existing Oracle Form module is reviewed to understand its fields, access structure, validations, and related database tables. A flowchart is created first so the usage flow and user interaction can be defined clearly before development starts. The web UI is built with Bootstrap and adapted from Oracle Form into a cleaner, more user-friendly layout for internal use.
