SCEGA — Government Event Licensing Platform

Overview

SCEGA is a Saudi government digital platform for event licensing and permitting workflows across conferences, exhibitions, workshops, gatherings, and related event types.

The wider solution connected a public applicant experience with government identity, verification, payment, notification, and workflow capabilities. This case study stays at a public-safe architectural level and focuses on my verified work in the public Angular portal and selected areas of its shared .NET backend.

My Contribution

I contributed full-stack, working primarily on reusable Angular infrastructure and complex public licensing flows while also implementing and refactoring selected backend capabilities.

My frontend work included configurable multi-step workflows, shared form controls, cross-field validation, server-backed file upload, bilingual interface patterns, and authentication-state integration. On the backend, I contributed authentication and authorization infrastructure, CQRS request handling, EF Core changes, API workflows, mapping configuration, and dependency-registration improvements.

• Designed shared Angular infrastructure that multiple licensing features could compose instead of rebuilding navigation and form behavior for each flow.
• Applied those patterns to workshop and gathering workflows, including modification, draft, validation, and API-integration behavior.
• Worked across frontend and backend boundaries while keeping the contribution distinct from ownership of the complete government solution.

Configurable Licensing Workflows

Complex licensing journeys needed consistent step navigation and validation without coupling reusable infrastructure to one event type. I designed a configuration-driven Angular stepper that let each workflow declare its own steps while sharing the mechanics around navigation, state, and validation.

The stepper supported dynamic step composition, linear and non-linear movement, asynchronous entry and exit guards, lifecycle hooks, conditional navigation, validation gates, scroll-to-error behavior, persistence, and protection against duplicate navigation. Strongly typed configuration kept each workflow explicit as requirements evolved.

Shared Forms, Validation & File Upload

I built shared controls that behaved as native participants in Angular Reactive Forms. A reusable server-backed file-upload control implemented the ControlValueAccessor contract so licensing forms could handle attachment identifiers, validation, disabled and read-only states, and value changes through the same form APIs as other inputs.

Edit flows added a second concern: persisted attachment identifiers had to be resolved into displayable file state and synchronized back into the form while add, remove, upload, and cancellation behavior remained predictable. The control handled that lifecycle without exposing storage details to feature components.

Authentication Across Frontend & Backend

I contributed to an authentication pipeline that connected enterprise Windows SSO with JWT-based API access. Server-side identity establishment, application provisioning, role and permission mapping, token creation, and application authorization remained separate responsibilities within the trust boundary.

A key rule was that an authenticated enterprise identity still had to be provisioned in the application before application claims were issued. This prevented identity-system access alone from becoming application authorization.

CQRS Workflows & Backend Refactoring

The ASP.NET Core backend used a clean, layered structure with CQRS and MediatR to keep application operations in focused command and query handlers. I contributed handlers, mappings, validation, API behavior, and EF Core data changes for workshop and gathering scenarios without treating CQRS as a distributed messaging design.

I also refactored a large, centralized dependency-registration area into coherent extension methods and reorganized AutoMapper and application-startup configuration. The change preserved existing wiring while making service groups and startup responsibilities easier to find and maintain.

• Kept request handling focused around explicit application operations.
• Improved the organization and discoverability of dependency configuration.
• Maintained clear boundaries between API, application, domain, and infrastructure concerns.

Delivery & Engineering Quality

I authored a GitHub Actions workflow for Angular build verification and contributed pull-request templates, contribution guidance, formatting conventions, and project-structure documentation. This work established repeatable validation and clearer repository expectations without implying ownership of the wider delivery platform.

Across the application, the same emphasis appeared in bilingual Arabic and English patterns, RTL-aware shared controls, explicit TypeScript contracts, subscription cleanup, guarded asynchronous navigation, and maintainable feature boundaries.