The Events module provides an list of various events that can trigger configured actions. When an Event is fired, it will invoke all of its configured actions.
Time and Calendar Events
TimeIntervalEvent
This interval will be triggered periodically after an set time interval.
- Interval: allows you to define the Time period after which the event will be triggered. After the event was triggerd, the period starts again
- ExecuteImmediatly: Allows you to execute the event once when the event is first started, and after that when the Interval is triggered
CalendarEvent
This event will trigger certain calendar events, such as Daily, ever Monday, every first of the month etc.
- RepeatMod: Defines if the event repeats every day, week or Month.}
- Daily: The event will repeat according to “DayOfMonth”
- Weekly: The event will repeat according to “WeekDays”
- Monthly: The event will repeat every month on the first day of the month.
- DayOfMonth: Sets the days of the calendar on which the event will trigger. This is only valid for RepeatMode = Daily
- WeekDays: Sets the days of the Week on which the event will trigger. This is only valid for RepeatMode = Weekly
- TimeOfDay: Defines the time of day when the event will trigger. Applies to all RepeatModes
Variable Events
VariableChangedEvent
This event will trigger, everytime an configured variable changes its value.
- VariableName: The Variable whos value change will trigger the event, if it maches the “CompareMode”
- CompareMode: Defines on which value the event will trigger
- None: The event will trigger on every value change
- <, >, <=, >=, =: The Variable value will be compared against the given “CompareValue” and will trigger if it matches
- CompareValue: If “CompareMode” is set to any value other than “None”, this is the value that the variable will be compared against, according to “CompareMode”
ScriptEvent
This event is similar to VariableChangedEvent, but it allows you to use up to 4 different variables and compare them against each other as you see fit. The event then fires, if the “Expression” returns true
- VariableName1: The Variable whos value change will trigger the event evaluation of the expression
- VariableName2: The Variable whos value change will trigger the event evaluation of the expression
- VariableName3: The Variable whos value change will trigger the event evaluation of the expression
- VariableName4: The Variable whos value change will trigger the event evaluation of the expression
- Expression: This expression allows you to use Mathematical expression such as “+,-,*,/” and comparisions such as “<, >, =” to evaluate the “VariablesValues” in the Expression. You can for example write: “<%EventVarValue1%> = <%EventVarValue2%>” to compare two variables against each other.
- EvaluateAfterStartup: Allows you to evaluate the expression once when the event is first started, and after that every time any of the Variables have changed.
System Events
UserChangedEvent
Triggers every time an user has changed in the VisXpert system. This also applies if the current user gets “logged out” since the user changes to user “Nobody”.
MachineInactivityEvent
Triggers if the system detects that no user inputs from any Mouse or Keyboard have been received.
- InactivityTime: the Tieme that no user input has been received before the evnet triggers
OperatingSystemEvent
Triggers if certain operating system events have happened.
- OSEvent: Defines the event that will trigger this event
- PowerModeChange: The PC has gone to Sleep, wakes up or similar
- SessionSwitch: the user is changeing the Windows user
- DisplaySettingsChagned: The Screen Resolution has chagned, an new monitor has been conected, etc.
- TimeChanged: The Windows time settings has changed, either by the user or by NTP. WARNING! this will also trigger if the time was changed by NTP Time synchronization.
- SessionEnded: the user is either logging out, or shutting down windows.
ProcessEvents
ProcessStartedEvent
Triggers if an Process of the given name has been started
- ProcessName: the Name of the processs the event should listen for
ProcessTerminatedEvent
Triggers if an Process of the given name has been terminated
- ProcessName: the Name of the processs the event should listen for
ModuleEvents
StartupEvent
Triggers as soon as the Events module has been started up
ShutdownEvent
Triggers as soon as the Events module has been shut down
Data Changed Events
FileSystemChangedEvent
Triggers when an file has been created, changed or been deleted in an specific directory. The event is
- Path: The Directory in which the event should listen. The event is only listening in the specified path, not in its subdirectories.
- Filter: The file filter to trigger this event. You can use wild card characters such as “*.txt” or “*.*” to listen for all text files or all files in general
- Delay: Allows you to delay the event after the file has changed, been created etc.
- FireOnChanged: The event will fire if an file that matches the filter in the given Path has changed
- FireOnCreated: The event will fire if an file that matches the filter in the given Path has been created
- FireOnDeleted: The event will fire if an file that matches the filter in the given Path has been deleted
- FireOnRenamed: The event will fire if an file that matches the filter in the given Path has been renamed
DatabaseChangedEvent
Triggers when any value in an database has been changed. The algorithm uses an tracking table where it stores some data to determine if an database has changed. It does not distinguish what data has changed, just that some data has changed.
- SQLConnectionString: the connection string to the database that should be monitored. The “InitialCatalog” property must hold the name of the database to watch.
- CheckIntervall: the intervall in which the database will be “polled” for changed. This also means, that this event can only be triggered at most after the Check intervall
- Delay: Allows you to delay the event after the database has changed, been created etc.
