Skip to main content

Antrix Portal

Purpose​

intt-portal is the main Angular frontend for the Antrix platform.

Local runtime facts​

  • main team run command: pnpm run start:stg or ng serve --configuration=staging
  • alternative direct command: ng serve --configuration=staging
  • config files: .env, src/environments/environment.staging.ts, src/proxy.conf.json
  • dockerized port in compose: 80
  • frontend developers typically clone only this repo and use staging-backed APIs

Owned modules​

Current structure documentation points to web modules such as:

  • CR
  • NTT
  • RNTT
  • CTT
  • GSB
  • Dashboards
    • CR
    • NTT
    • CTT
  • Reports
    • CR
    • NTT
    • CTT
    • GSB
    • Audit Trail
  • Settings
  • Profile

Dependencies​

  • browser runtime
  • staging environment access for current team flow
  • .env keys for crypto and client secrets
  • auth, setting, data, and domain APIs through staging endpoints

Required config groups​

  • PUBLIC_KEY, PRIVATE_KEY, SECRET_KEY
  • CLIENT_SECRET_STG, CLIENT_ID_STG
  • CLIENT_SECRET_PRD, CLIENT_ID_PRD
  • VOC_TOKEN, OIP_VOC_TOKEN
  • OIP_SMARTMAP_API_KEY, OIP_SMARTMAP_AUTHORIZATION

What it does​

Based on the current project documentation, the portal:

  • handles login and SSO callback flows
  • stores authenticated user context
  • renders the main application shell
  • lazy-loads business modules and dashboards
  • calls backend APIs through a shared API service layer

Key technical notes​

  • Angular SPA
  • NgModule-based architecture
  • PrimeNG for UI
  • NGXS for state
  • OIDC client integration
  • hash-based routing

Main commands​

Install:

pnpm install

Run locally:

pnpm run start:stg

or

ng serve --configuration=staging

Build:

pnpm run build

Test:

pnpm run test

or

ng test --code-coverage

Staging API references​

Frontend developers currently use staging Swagger endpoints as the reference for API discovery:

  • https://intt-stg.tm.com.my/ticket/docs#/
  • https://intt-stg.tm.com.my/setting/docs#/
  • https://intt-stg.tm.com.my/data/docs#/
  • https://intt-stg.tm.com.my/auth/docs#/

Delivery flow​

Current frontend delivery path:

<feature-branch> -> development -> staging

Delivery path to Production:

staging -> ak-prod -> production

QA validation target:

  • https://intt-stg.tm.com.my/

Upstream and downstream​

  • upstream caller: browser user
  • downstream systems: auth, setting, data, ticket, GSB, and other domain APIs through environment-based base URLs

Existing documentation source​

The portal already contains internal structure notes in:

  • intt-portal/docs/application-structure.md

That file was used as the base for the architecture summary pages in this site.

Local testing​

  • unit tests: pnpm run test
  • CI-style tests: pnpm run test:ci