Case 05 of 10

inRol

Student enrolment, supporting registration and administrative workflows.

• My part: Contributed (owned features, logic or change requests)
• Role: Feature owner
• Where: Pexus product suite · ING Tech
• 6+ tenants

The picture on this page is a concept illustration, not a product screenshot.

The problem

New business needs have to land in a system institutions already rely on. Every enhancement has to fit existing data and workflows, and serve tenants whose requirements differ.

My responsibility

Feature ownership: features, enhancements and change requests, not a rebuild of the system.

• Owned delivery of dynamic student contract generation, including Devanagari support.
• Worked on bus card generation.
• Worked on major product improvements while supporting the existing system.

Decisions and contributions

• Localisation: generated documents must render Devanagari correctly, not only display it on screen.
• Operations: enrolment covers more than registration, so artefacts like bus cards belong in the same flow.

Challenges and trade-offs

• Changes have to coexist with existing data, workflows and tenants already in production.
• Requirements differ across 6+ tenants and have to be reconciled within one system.

Outcomes

Dynamic student contracts with Devanagari support and bus card generation, delivered into a live system used by 6+ tenants.