Every lifecycle event in PeopleVizio fires an in-process Spring event. Notification engine, analytics projector, document generator all subscribe — and so can our customers. Here's how.
The classic HRMS problem is that any customisation requires a fork. Customer wants a Slack message when a promotion happens? Ticket for the vendor; wait six months.
PeopleVizio treats domain events as the integration seam. When an employee is hired, an EmployeeHired event fires in-process. The notification engine subscribes to it; the analytics projector subscribes to it; the letter generator subscribes to it. Customers can subscribe to it too — through a managed Kafka topic on Enterprise, or a signed webhook on Growth.
This means no forks. Every customisation is a listener. Every listener is isolated. Every piece of custom logic can be swapped without touching the core platform.