--- title: Managing Triggers in Cognos Analytics description: Triggers are one of the most useful things that exist for managing events in any Cognos environment, but to be managed effectively to access them quickly, easily and selectively whenever needed. NetVisn makes it virtually painless. image: https://www.envisn.com/hubfs/dominoes.png --- [![envisn](https://www.envisn.com/hs-fs/file-15282154-gif/images/logo.gif?width=120&name=logo.gif "envisn")](https://www.envisn.com) [![Request a Demo](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/70307/973f9256-ef61-4ab8-ab2d-a004a90a18be.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/70307/973f9256-ef61-4ab8-ab2d-a004a90a18be) [![cognos security as youve never seen it - learn more about netvisn](https://www.envisn.com/hs/cta/cta/default/70307/3166c389-8135-4d84-9988-99dc8d523426.png)](https://www.envisn.com/hs/cta/cta/redirect/70307/3166c389-8135-4d84-9988-99dc8d523426) # Envisn's IBM Cognos Blog ## [Managing Triggers in Cognos Analytics](https://www.envisn.com/envisn-cognos-blog/managing-triggers-in-cognos-analytics) Posted by [The Envisn Team](https://www.envisn.com/envisn-cognos-blog/author/the-envisn-team) - [Tweet](https://twitter.com/share) *![triggers in cognos](https://www.envisn.com/hs-fs/hubfs/dominoes.png?width=282&name=dominoes.png)By Paul Hausser, [Envisn, Inc.](https://www.envisn.com/)* Triggers are widely used across many Cognos environments, particularly larger ones where reports are often scheduled based on one or more dependent events being completed. These events are typically things external to Cognos but required by it to complete a scheduled event. An example would be to run reports based on the successful update of the data warehouse. If the reports were simply run on a time schedule it’s possible that the reports could kick off before the data warehouse update was completed rendering the reports useless and requiring a rerun. Tying report execution to a successful update of the data warehouse insures that they will only be run once for a given cycle. Creating triggers is reasonably easy once the Cognos environment has been enabled for this and the trigger has been created and tested within the warehouse server. It only needs to be given a name and entered into the schedule for one or more reports on Cognos. This is a great feature since it enables things to be done much more efficiently within Cognos while at the same time tying in external events for operational effectiveness. What often happens over time as things change is that triggers accumulate and get created with a multitude of different names. And since there is no way of easily identifying objects using triggers within Cognos, or the names of the triggers, or where the same triggers is used multiple times, this can be a real problem when changes occur. To successfully deal with this we created the capability within our [**NetVisn**](https://www.envisn.com/netvisn) product to better manage triggers across the Cognos environment. We wanted the ability to manage triggers in a manner that gives the NetVisn user the flexibility to easily get the information they need at any given time and at the same time get this information output in a way that best meets their needs. Thus, in ***figure 1*** we have the ability to choose what we want and how we want it organized. We can select all triggers or specific triggers that exist in our environment. We also have the ability to determine if we want the output organized by location, trigger name, package, etc. ![trigger dependency in cognos](https://www.envisn.com/hs-fs/hubfs/triggers-fig-1.jpg?width=800&name=triggers-fig-1.jpg) We also have the ability to get a total count of triggers, a count by trigger name, etc. Additional detail data such as creation date, enabled/disabled, etc. can also be selected. In an environment with a large number of triggers having the ability to get the specific data needed on triggers is critical. ***Figure 2*** shows the analysis options we’ve selected along with a total count for all triggers in our environment. ![cognos trigger analysis](https://www.envisn.com/hs-fs/hubfs/triggers-fig-2.jpg?width=541&name=triggers-fig-2.jpg) Finally, in ***figure 3*** we see eight of the triggers organized by trigger name along with along with other information on location, creation date, package name and its status. Note that one of the triggers is currently disabled. ![cognos triggers in netvisn](https://www.envisn.com/hs-fs/hubfs/triggers-fig-3.jpg?width=800&name=triggers-fig-3.jpg) Triggers are one of the most useful things that exist for managing events in any Cognos environment. In fact, without them many things currently being done would not be possible. But since change is part of every environment, triggers need to be managed effectively and that requires an ability to access them quickly, easily and selectively whenever needed. Having the right tool with which to do this makes it virtually painless. *© [Envisn, Inc.](https://www.envisn.com/netvisn) – 2019 – All Rights Reserved.* *[![Learn More about NetVisn](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/70307/c93ed13b-725a-49f4-9957-a389ed05974a.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/70307/c93ed13b-725a-49f4-9957-a389ed05974a)*   Topics: [Cognos BI Best Practices](https://www.envisn.com/envisn-cognos-blog/topic/cognos-bi-best-practices), [Cognos Analytics](https://www.envisn.com/envisn-cognos-blog/topic/cognos-analytics), [Cognos Triggers](https://www.envisn.com/envisn-cognos-blog/topic/cognos-triggers) *Your feedback is very important to us - we’d love to hear your comments!* ### Subscribe to Envisn's IBM Cognos Blog [![Learn how Netvisn can solve your specific needs and challenges Sign Up for a Personalized Demo](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/70307/c764cb9d-e3c2-4a91-9564-d666f1f5c7e1.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/70307/c764cb9d-e3c2-4a91-9564-d666f1f5c7e1) ### Posts by Category - [Cognos Content Store (22)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-content-store) - [Cognos BI Best Practices (21)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-bi-best-practices) - [Cognos Analytics (19)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-analytics) - [Cognos BI administration (19)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-bi-administration) - [Cognos Security (18)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-security) - [Cognos Tools (14)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-tools) - [Cognos Audit Data (11)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-audit-data) - [Cognos Reporting (9)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-reporting) - [Cognos Auditing (8)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-auditing) - [Cognos 10 (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-10) - [Cognos Framework Manager (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-framework-manager) - [Cognos Metadata (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-metadata) - [BI Trends (6)](https://www.envisn.com/envisn-cognos-blog/topic/bi-trends) - [IBM Information on Demand (6)](https://www.envisn.com/envisn-cognos-blog/topic/ibm-information-on-demand) - [Cognos Audit Log (5)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-audit-log) - [cognos impact analysis (4)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-impact-analysis) - [Big Data (3)](https://www.envisn.com/envisn-cognos-blog/topic/big-data) - [Cognos Data Sources (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-sources) - [Cognos Documentation (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-documentation) - [Cognos Scheduling (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-scheduling) - [Product Information (3)](https://www.envisn.com/envisn-cognos-blog/topic/product-information) - [cognos data lineage (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-lineage) - [Archiving Cognos Content (2)](https://www.envisn.com/envisn-cognos-blog/topic/archiving-cognos-content) - [Cognos FM Model (2)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-fm-model) - [Cognos migration (2)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-migration) - [Announcements (1)](https://www.envisn.com/envisn-cognos-blog/topic/announcements) - [Cognos Change Management (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-change-management) - [Cognos Data Provenance (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-provenance) - [Cognos Hotfiles (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-hotfiles) - [Cognos Powerplay (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-powerplay) - [Cognos Triggers (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-triggers) - [Consolidating Cognos Environments (1)](https://www.envisn.com/envisn-cognos-blog/topic/consolidating-cognos-environments) - [Impromptu (1)](https://www.envisn.com/envisn-cognos-blog/topic/impromptu) - [Merging Content Stores (1)](https://www.envisn.com/envisn-cognos-blog/topic/merging-content-stores) - [Remote Cognos Management (1)](https://www.envisn.com/envisn-cognos-blog/topic/remote-cognos-management) - [cognos deployments (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-deployments) - [cognos fm model documentation (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-fm-model-documentation) - [cognos workspace (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-workspace) - [netvisn (1)](https://www.envisn.com/envisn-cognos-blog/topic/netvisn) [see all](https://www.envisn.com/envisn-cognos-blog/managing-triggers-in-cognos-analytics#) ### Posts by Popularity [![free download expert guide to cognos audit data](https://www.envisn.com/hs/cta/cta/default/70307/6933ba0f-4664-4d5d-9413-edf64d7b2644.png)](https://www.envisn.com/hs/cta/cta/redirect/70307/6933ba0f-4664-4d5d-9413-edf64d7b2644) ### [Cognos Tools from Envisn](https://www.envisn.com/envisn-products) [NetVisn](https://www.envisn.com/netvisn) [AutoVisn](https://www.envisn.com/autovisn-cogos-scheduler) [UniVisn](https://www.envisn.com/univisn-cognos-performance-management) [DocuVisn](https://www.envisn.com/docuvisn-cognos-documentation) ### [Cognos Resources](https://www.envisn.com/resources) [Envisn’s IBM Cognos Blog](https://www.envisn.com/envisn-cognos-blog) [Custom Query Library](https://www.envisn.com/custom-query-library) [Tutorial Videos](https://www.envisn.com/cognos-demo-videos) [Mastering Cognos Security](https://www.envisn.com/mastering-ibm-cognos-security) [Content Store Survival Guide](https://www.envisn.com/content-store-survival-guide) [Expert Guide to Cognos Audit Data](https://www.envisn.com/cognos-audit-data-expert-guide) ### [Contact Envisn](https://www.envisn.com/contact) [Request a Demo](https://www.envisn.com/request-a-demo) [Support](https://www.envisn.com/support) 512-991-3999 [info@envisn.com](mailto:info@envisn.com) ### Latest Cognos Posts | [![youtube](https://www.envisn.com/hs-fs/hubfs/youtube.png?width=30&name=youtube.png)](https://www.youtube.com/user/envisn) | [![linkedin](https://www.envisn.com/hs-fs/hubfs/linkedin.png?width=30&name=linkedin.png)](https://www.linkedin.com/company/envisn-inc./) | [![twitter](https://www.envisn.com/hs-fs/hubfs/twitter.png?width=30&name=twitter.png)](https://twitter.com/Envisn) | [![facebook](https://www.envisn.com/hs-fs/hubfs/facebook.png?width=30&name=facebook.png)](https://www.facebook.com/envisn/) | | --- | --- | --- | --- | [![Real Time Analytics](https://static.getclicky.com/media/links/badge.gif)](http://clicky.com/101126274) ![Clicky](https://in.getclicky.com/101126274ns.gif) 3000 Polar Lane, Suite 901, Cedar Park, TX 78613 USA *Serving North America, Europe, and the UK with plans to expand to other areas in the near future. **[Privacy, Copyright & Liability](https://www.envisn.com/privacy-copyright-liability)*