Let’s say you need to add the following confidentiality statement to each of your footers in dozens of existing Cognos reports: “The information contained within this report is proprietary and confidential. No part of this report may be disclosed in any manner to a third party without prior written consent.”
IBM Cognos and Motio Best Practices Blog
In this follow up to my first post about filters. I am going to briefly talk about number filters in MotioPI Professional. Without further ado, let’s dive into number property filters in MotioPI!
Number Property Filters
Number Property filters in MotioPI are just what they sound like, filters that act on any numerical property of your content. Examples include, but are not limited to: run duration of a report in seconds, the total number of recipients set on a schedule and the size of an output. I will talk briefly about how to set up a Number Property filter and then show them in action for the three examples I listed above.
Have you ever lost or corrupted a Cognos Framework Manager Model? Have you ever wished you could recover the lost model based on information which is stored in your Cognos Content Store (e.g. a package which was published from the lost model)? You're in luck! You can use MotioPI (a free tool for Cognos admins) to recreate your Framework Manager Model's "model.xml" file with just a few simple clicks.
Filtering In MotioPI
One of the most powerful features in MotioPI is its ability to filter search results. Intelligent usage of filters will enable you to answer complex questions about your environment easily via MotioPI. Using filters isn’t always as simple as just clicking "Search." In this blog post, I’ll provide general instructions on how to use filters, and then go in depth on a few filter types. Specifically, I am going to talk about text property filters.
What can filters do for me?
A common question that keeps getting asked of the MotioPI Support Staff is how to identify IBM Cognos reports, queries, etc. that utilize in-line SQL in their specifications. While most reports leverage a package to access your data warehouse, it is possible for reports to run SQL statements directly against the database, bypassing your package. Let's talk about why it's important to know which reports have embedded SQL.
The launch of IBM Cognos Analytics marked the release of many new features along with phasing out many mainstays of previous Cognos versions. One of these new features is a type of report, called a “fully interactive” report. Fully interactive reports have additional capabilities when compared to reports that are not fully interactive reports (sometimes called “limited interactivity”).
So what is a fully interactive report? Fully interactive reports are a new way to author and view reports in Cognos Analytics. Fully interactive reports enable live analysis of the report. This live analysis comes in the form of toolbars that enable the user to filter and group information or even generate charts. All this without re-running your report!Image Source:IBM Analytics
One of MotioPI Pro's basic fundamentals is to improve workflows and how administrative tasks are done in IBM Cognos in order to "give time back" to Cognos users. Today's blog will discuss how to improve the workflow around editing Cognos Framework Manager model element names, descriptions, and tooltips. We will demonstrate a MotioPI Pro feature that makes it easy to update the information that business users see- model terminology elements.
Creating shortcuts in Cognos is a convenient way to access the information you use frequently. Shortcuts point to Cognos objects such as reports, report views, jobs, folders, and so on. However, when you move objects to new folders/locations within Cognos, the shortcuts that reference them turn into broken links. You would then have to go into Cognos and recreate all of the shortcuts to those objects that were moved.
Or, you could conveniently move the Cognos objects within MotioPI Pro in order to prevent broken shortcuts and avoid the pain of having to recreate them.
In some situations employees leave companies and the organization has not fully prepared for their exit. One specific scenario when an employee leaves that causes a great deal of extra work on IBM Cognos administrators involves the ex-employee's scheduled jobs, reports, etc.
Let's say that Ed has configured many scheduled jobs and reports that go out to a number of people, but he has left the company. Shortly after Ed's last day, several of these people are not receiving their scheduled Cognos reports. These employees contact their administrator. The administrator investigates and sees that these specific failed reports are attempting to use Ed's account and since he has left the company, his account in LDAP is inactive, causing the reports to fail.
In IBM Cognos, schedules are associated with a "credential," which is a security token that is associated with a Cognos user. In this case, Ed's schedules execute and authenticate through his credential. His stored credential passes to the authentication source (e.g. LDAP, Active Directory, etc.) to get logged in. After an employee leaves, their account becomes inactive in LDAP, AD, or the like, and all of their many scheduled jobs and reports will fail. The Cognos admin is then tasked with figuring out how to find and then reassign all of the ex-employee's schedules.
In Cognos, there is no easy way to do this. There is no search feature that allows you to find all schedules that use a specific Cognos user's credential.
We've heard from several Cognos users recently who would like to be able to quickly retrieve and view the permissions for more than just Cognos reports. While you can do this in Cognos Connection, it will only allow you to view permissions on each Cognos object one at a time.