Event Triggers

Event Triggers use scripts to create an Event Filter that listens to events passing through the MVI Event Service. When the Event Script detects an event (e.g., that a dependency of the trigger’s workflow is used; a completed build of a related project; or a completed originating workflow with the auto-deploy flag set to "true"; etc.), it can then trigger another action by the MVI server.

In general, once configured, the scripts are immediately active and listening for events. The trigger, workflow, and project parameters provide references to the Event Trigger itself, as well as the workflow and project it belongs to. The MVI API exposes its event service so the Trigger may be configured to listen for specific events.

Prerequisites

You must have Administrative permissions. Prior to adding an Event Trigger to the workflow, the Event Script must be created. If you are unfamiliar with MVI scripting, Scripting and Tools > Developer Tools before creating an Event Trigger.

Create Event Trigger

Go to Administration and select the workflow the trigger is to be added to.
Select the Triggers tab, and click the New Trigger button.
Select Event Trigger from the drop-down menu and click Select.
Configure trigger:

Name the trigger.
Force. Check the box to force a build every time this trigger executes.
Event Script. Select the script that returns an Event Listener. Available parameters are the workflow to be triggered (workflow); this project (project); and this trigger (trigger).

Click Save then Done.

Repository Triggers
For Continuous Integration builds, it is ideal to build every time a file is checked in. In this case, a post-commit script is added to the SCM that alerts MVI of source changes. Once the Repository Trigger is active for a workflow, every commit of source changes will initiate a build.

Go to Administration and select the workflow the trigger is to be added to.

If using Subversion, triggers can be set up at the repository level. Once done, they are available to all workflows using that repository. An individual workflow trigger does not need to be created.

Select the Triggers tab, and click the New Trigger button.
Select Repository Trigger from the drop-down menu and click Select.
Configure trigger:

Name the trigger.
Force. Check the box to force a build every time this trigger executes.

Event Triggers
Champaign Urbana Limousine Service Ecommerce Software Services & Packages PPC Campaign Pay Per Click Management Overview of Events and Behavior Tracking Custom Performance Tracking Reports Limousine Rentals Weddings and Ceremonies Content Management Systems MVI Internet Marketing Strategy The Importance of Event Tracking in Web Analytics Limousines in Idaho Web Hosting MVI Reporting & Analytics SEO Investments On The Rise Wedding Limousine Rental Tips Limopros in Phoenix Reporting & Analytics Adding Event Triggers for Interactivity Custom Web Application Development Web Application Development Outsourcing Company LIMOPROS USA Limousine Party Bus Limo Bus Charter Bus Services Web Site Content Writers ECommerce Development Company Real-Time Web Site Tracking Getting Started Tracking Prom Limo Service in San Francisco Limoprose For All Events and Occasions Quality Ecommerce Website Design Service Web Site Visitor Tracking Las Vegas Car Service and Limo Service Corporate Events Limo Toronto The Hunt for Stats Tracking Email and Clear Pixels San Francisco Limo Service Why Are Our Tanning Beds Different Customer Relationship Management (CRM) What Is It MVI Internet Marketing Trigger Events and Selective Perception Triggered Campaigns 3 Things to Keep In Mind The Safety Of Indoor Tanning E-Commerce Solutions MVI Web Design Solution Enabling and Disabling Triggers Trigger Event Strategist Glaucoma Internet Marketing Services Customer Relationship Management Application Airport Services Indoor Tanning Accessories For Men and Women Event Triggers (Methods) Windows7 Trigger Start Services Guaifenesin Wedding Limo Georgia Style Home Tanning Bed Strategic Planning & Marketing Strategies Enable Growth Pay Per Click Advertising Generates Targeted Leads Thinking About Security Monitoring and Event Correlation Herpes zoster Choosing the ideal Limo Service Which Indoor Tanning Accessories Are For You Web Development Solutions Lead Management System The Talent Of Event-Triggered E-mail Triggers To Event Cardiomyopathy Wedding Limo Service Forget all those home tan products Pay Per Click (PPC) Management Internet Marketing Services Creating Custom Event Triggers In Task Scheduler Event Triggers Acromegaly Improve Cross-Selling To Customers With Event Triggered Marketing Event Handlers Archive for the Automated Emails, Event Trigger Marketing Category Web Designing Company Analytics Services Search Engine Marketing (SEM) Strategies SEO Friendly web design competitive advantage Visitor Tracking Web Site Visitor Tracking Website Tracking System Real-Time Visitor Tracking System Website Traffic Statistics and Web Analytics	Event Triggers use scripts to create an Event Filter that listens to events passing through the MVI Event Service. When the Event Script detects an event (e.g., that a dependency of the trigger’s workflow is used; a completed build of a related project; or a completed originating workflow with the auto-deploy flag set to "true"; etc.), it can then trigger another action by the MVI server. In general, once configured, the scripts are immediately active and listening for events. The trigger, workflow, and project parameters provide references to the Event Trigger itself, as well as the workflow and project it belongs to. The MVI API exposes its event service so the Trigger may be configured to listen for specific events. Prerequisites You must have Administrative permissions. Prior to adding an Event Trigger to the workflow, the Event Script must be created. If you are unfamiliar with MVI scripting, Scripting and Tools > Developer Tools before creating an Event Trigger. Create Event Trigger Go to Administration and select the workflow the trigger is to be added to. Select the Triggers tab, and click the New Trigger button. Select Event Trigger from the drop-down menu and click Select. Configure trigger: Name the trigger. Force. Check the box to force a build every time this trigger executes. Event Script. Select the script that returns an Event Listener. Available parameters are the workflow to be triggered (workflow); this project (project); and this trigger (trigger). Click Save then Done. Repository Triggers For Continuous Integration builds, it is ideal to build every time a file is checked in. In this case, a post-commit script is added to the SCM that alerts MVI of source changes. Once the Repository Trigger is active for a workflow, every commit of source changes will initiate a build. Go to Administration and select the workflow the trigger is to be added to. If using Subversion, triggers can be set up at the repository level. Once done, they are available to all workflows using that repository. An individual workflow trigger does not need to be created. Select the Triggers tab, and click the New Trigger button. Select Repository Trigger from the drop-down menu and click Select. Configure trigger: Name the trigger. Force. Check the box to force a build every time this trigger executes.
Copyright © 2012 http://www.sagercorp.com