When maintaining process quality across large enterprise modeling teams, catching semantic errors after a model is saved to the database is often too late.
To enforce quality rules instantly, client-side event listeners and macros in ARIS Architect can intercept modeler actions in real time and validate rules before persisting changes to the backend.
Here is a breakdown of how the 5 architectural layers interact during event-driven validation:
- 1. Modeler Action (Client UI): A modeler updates an object attribute, creates an occurrence, or triggers a save action directly on the active canvas.
- 2. Event Listener Layer: The ARIS Architect event handler traps the vetoable event (e.g.,
Model is to be saved) and temporarily suspends the save operation. - 3. Macro Execution Layer: Loads and executes the JavaScript rules engine (
Script Rules.js) bound to that specific event trigger. - 4. Execution APIs Layer: Evaluates model relationships and semantic governance constraints against the ARIS Scripting API to calculate validation results.
- 5. ARIS Server & Database Layer:
- If validation fails: The client UI displays a custom error dialog and cancels the save (issuing a veto).
- If validation passes: The request is passed to the application server to safely commit the transaction to the backend RDBMS database.
Keeping real-time client-side validation logic decoupled from application server processing makes custom governance frameworks significantly cleaner and easier to scale.