Triggers are core to Ouvvi and are like external events, you attach Triggers to Projects to run them automatically. Typically Triggers are Time based i.e. Every 10 minutes however triggers can also be created from external systems like when Data Changes in SQL, CRM, SharePoint etc.
Triggers are evaluated on an internal time-clock the default is every 30 seconds. When the Trigger evaluation starts Ouvvi will put all the triggers on the queue and the Ouvvi service agent(s) will start processing the triggers. The Triggers are all run in Parallel based on the number of Threads the Ouvvi service agent(s) have available. Once all the triggers have be evaluated Ouvvi will then calculate which one(s) will fire and start any projects attached to those triggers.
All the triggers are based on Time and when the value is greater than the current stored value the Trigger will fire.
For Ouvvi v3 Triggers can now return a long/int value and the time is calculated based on the current time.
The Atom Trigger fires based on a change to the modified date value in an Atom Feed.
The CRM Entity Trigger fires based on a change in a CRM Entity, This Trigger looks at the modifiedon field and fires when this value increases.
The Date Trigger fires on a specific Day of the Month and at a Specific Time.
The Exchange Server Mailbox Trigger fires when a new email message is received in an Exchange Mailbox Inbox.
The File Trigger fires when a file is modified.
The Folder Trigger fires when a Folder is modified, i.e when a new file is created in the folder.
The Ftp Trigger fires when a file is modified on an FTP server (FTP and FTPS)
The Http Trigger fires when a web page returns a DateTime value.
The Json Trigger fires when a Http request returns a Json document and checks for a DateTime value in the Json.
The OData Trigger calls an OData V1/V2 service and fires when the returned value increases.
The Program Trigger runs an external program and reads the DateTime value from the StdOutput stream.
The SharePoint List Trigger fires when there is a change to a SharePoint List.
The Simego Change Service Trigger fires when there is a change to an item on the Simego Change Service
The SQL Trigger runs a SQL Query and uses the result to fire the trigger.
Type of Connection String (Optional: provided by Connection Library)
Database Connection String (Optional: provided by Connection Library)
The maximum time the SQL command can run before returning an error.
The SQL Query to run the query must return a single result.
Example Query below that returns the maximum value of the Modified Column in the Table MyTable
SELECT MAX([Modified]) FROM [MyTable]
The Time Interval Trigger fires on a regular time interval like every 10 minutes.
The Days this Trigger will run.
The time period where this trigger is active in a TimeSpan format hh:mm:ss i.e. 08:00:00
The repeat time interval in a TimeSpan format hh:mm:ss i.e. 00:10:00 for 10 minutes.
The Time Trigger fires at a specific time on selected Days.
The XML Trigger calls a remote service that returns an XML document and uses XPath to fire based on the value from the XPath Expression.