-
Notifications
You must be signed in to change notification settings - Fork 4
Event rule
Ryan Newington edited this page Sep 4, 2025
·
8 revisions
Event Rules provide a mechanism for detecting and responding to user-created Exit events and Pre-operation events within ACMA's processing pipeline. These rules enable event-driven automation and conditional processing based on specific events raised during object lifecycle management.
Event Rules enable:
- Event-driven automation: Trigger constructors based on specific events
- Conditional processing: Execute logic only when specific events occur
- Cross-object communication: Respond to events from related objects
- Workflow orchestration: Coordinate complex business processes
- State-based reactions: React to system state changes and transitions
- Temporal processing: Handle time-based events and conditions
Events in ACMA consist of fundamental components:
- Event Name: Unique identifier for the type of event
- Sender: The object that raised the event
Event Rules can respond to different categories of events:
- Exit events: Events raised during object processing
- Pre-operation events: Events raised before synchronization operations
# Import ACMA PowerShell module
Import-Module AcmaPS
# Connect to ACMA database
Connect-AcmaEngine
# Send manual event for testing
$targetObject = Get-AcmaObject -ID $objectId
Send-AcmaEvent -ObjectId $targetObject.ObjectId -EventName "testEvent"
Event Rules provide the foundation for sophisticated event-driven automation within ACMA, enabling responsive and intelligent object processing that adapts to changing business conditions and system states.