Case 03 · Cloud and documents
A traceable cloud document library
Historical recovery, daily storage and authorized retrieval of operational documents through OneDrive, APIs and monitored processes.
- Company
- Fashion’s Park
- Business area
- Credit card operations
- My role
- Responsible for full-stack development, integrations, data processes and the technical evolution of the solution.
01
Context and challenge
Documents were originally stored on local infrastructure. Following an infrastructure incident, the company needed to recover historical documents and build a safer solution for storing and retrieving the documentation generated each day.
The materials included signed contracts, authorizations to access account information, card origination documents, insurance records, call recordings in which customers confirmed acceptance, and vouchers for purchases or cash advances made with the commercial card.
The solution had to recover historical information from provider APIs while also storing newly generated documents in the cloud every day.
02
The solution
- 01RecoverProvider APIs
- 02ProcessBatch · Python · Airflow
- 03CentralizeGraph · OneDrive
- 04RetrieveAngular · authorized access
Conceptual representation. It contains no real documents, recordings, identifiers, providers or internal interfaces.
Documentation was centralized in OneDrive through a Microsoft Graph integration. Daily batch processes ingested the documents and made them available for retrieval, monitoring and audit.
I also developed an administrative web application for the call center team. Users could search for documents associated with a customer through an identifier, browse documents by date and apply filters. The platform also supported authorized retrieval of call recordings and other evidence related to card operations.
The solution included APIs to:
- Integrate Microsoft Graph and OneDrive.
- Recover historical documents from providers.
- Centralize documents and their traceability.
- Expose documentation to other authorized company channels.
03
Technical work
My responsibility covered the interface, integrations, storage, security and process operations:
- Frontend development with Angular.
- API development with Flask and Python.
- Integration with Microsoft Graph.
- Document storage and organization in OneDrive.
- Authentication through Active Directory.
- Access control and permissions.
- SQL Server database design and maintenance.
- Scripts for overnight processes.
- Airflow integration for process monitoring.
- Historical data recovery and processing.
- Queries, filters and views for the operations team.
- Integration with the card application and website when appropriate.
04
Impact
The solution ran in production and made it possible to:
- Recover historical documentation through provider APIs.
- Centralize documents in OneDrive.
- Keep newly generated daily documents available.
- Make historical records easier for the call center to retrieve.
- Improve document traceability and control.
- Reduce manual searches.
- Prepare information for other digital channels.
- Run overnight processes monitored through Airflow.
The result was a searchable, traceable document library designed to support daily operations.