The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

One thing we couldn't accomplish though is opening the reports or dashboards in the same cognos window because it overwrites the already opened reports or dashboards and they all disappear from the switcher; so we are opening all objects accessed from this page in new windows.

If you want to open a report/dashboard (or any other perspective) by adding it to the switcher of the current Cognos page (as opposed to completely replacing the current page in the browser) you can do this with the openAppView method, e.g.

The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

One thing we couldn't accomplish though is opening the reports or dashboards in the same cognos window because it overwrites the already opened reports or dashboards and they all disappear from the switcher; so we are opening all objects accessed from this page in new windows.

If you want to open a report/dashboard (or any other perspective) by adding it to the switcher of the current Cognos page (as opposed to completely replacing the current page in the browser) you can do this with the openAppView method, e.g.

The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

One thing we couldn't accomplish though is opening the reports or dashboards in the same cognos window because it overwrites the already opened reports or dashboards and they all disappear from the switcher; so we are opening all objects accessed from this page in new windows.

If you want to open a report/dashboard (or any other perspective) by adding it to the switcher of the current Cognos page (as opposed to completely replacing the current page in the browser) you can do this with the openAppView method, e.g.

The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

One thing we couldn't accomplish though is opening the reports or dashboards in the same cognos window because it overwrites the already opened reports or dashboards and they all disappear from the switcher; so we are opening all objects accessed from this page in new windows.

If you want to open a report/dashboard (or any other perspective) by adding it to the switcher of the current Cognos page (as opposed to completely replacing the current page in the browser) you can do this with the openAppView method, e.g.

The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

`{	"name": "CustomizedTab",	"extensions": [		{			"perspective": "home",			"features": [				{					"id": "com.ibm.caHome.customizedTabFeature",					"collectionItems": [						{							"containerId": "com.ibm.bi.caHome.navigator",							"id": "com.ibm.bi.caHome.navigator.customizedTab",							"name": "customizedTab",							"label": "Today's News",							"weight": 600,							"module": "v1/ext/CustomizedTab/js/CustomizedTabView",							"properties": {}						},						{							"containerId": "com.ibm.bi.caHome.navigator",							"id": "com.ibm.bi.caHome.navigator.reportTab",							"name": "reportTab",							"label": "Sales Map",							"weight": 2,							"module": "v1/ext/CustomizedTab/js/ReportTabView",							"properties": {}						},						{							"containerId": "com.ibm.bi.caHome.navigator",							"id": "com.ibm.bi.caHome.navigator.customizedNavigatorTab",							"name": "customizedNavigatorTab",							"label": "Latest sales reports",							"weight": 0,							"properties": {								"path": ".public_folders/Sales Reports",								"toolbar": [									"filter",									"sort",									"refresh",									"settings"								],								"listOptions": true							}						}					]				}			]		}	]}​

One thing we couldn't accomplish though is opening the reports or dashboards in the same cognos window because it overwrites the already opened reports or dashboards and they all disappear from the switcher; so we are opening all objects accessed from this page in new windows.

If you want to open a report/dashboard (or any other perspective) by adding it to the switcher of the current Cognos page (as opposed to completely replacing the current page in the browser) you can do this with the openAppView method, e.g.

The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

The first one was an absolute nightmare. Since I was modifying the underlying xsl files every time there was an upgrade or patch I had to redo all of the changes.

The latest one is far more stable. For the most part I'm either using the published API for interacting with prompts, or adding features to Cognos. The links panel (and the dropdown menus, more info, prompts, and email pane) uses a div with CSS transitions (https://www.w3schools.com/css/css3_transitions.asp). The links themselves are standard drillthrough definitions.

The graph switcher is also something similar. It simply switches between two divs. The tricky part here is that I need to avoid using display:none in the CSS, or the native JS graphs won't size correctly. 

The export to Excel and PDF buttons just use Cognos Mashup Services in the backend to run the report. With that support is guaranteed until at least version 12. 

The responsive layout is by using flexbox. In this demo I was lazy and just used a series of HTML items, but it is possible to define local classes with the necessary settings. I haven't figured out how to embed media queries in the local classes, so those would have to be an HTML item.

Ultimately unless Cognos stops using HTML (unlikely) it should continue to work. There might need to be some tweaks here and there if there are structural changes to the generated HTML items, but this report specifically did not need any work when upgrading from 11.1.5 through 11.2.1. 

There are some things here that do use some undocumented APIs or features. If you were to take Cognos and shrink the page like I'm showing above, the iframe holding the report wouldn't let the width go that low. For some reason there's a min-width set. So I have a custom control that looks for the min-width and removes it. The email button also relies on a few undocumented API calls. From the Cognos point of view, clicking on that looks exactly as if the user clicked "Run As" and manually set the report to email. Any changes to those calls would require rewriting the APIs.

There are also a few more customizations. For one in version 11.1 it was possible to add an image to the upper left of the App Bar. For some reason that got removed in 11.2. https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=roles-creating-themes vs https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=roles-creating-themes (brandIconSmall was removed). And since we can't embed our own CSS file in the themes zip, I had to write an extension to hold the CSS styles specifically to add that logo back into the upper left corner.

This also didn't work between 11.1 and 11.2 because the HTML structure changed.

Hello Jim,

This customized welcome page looking is very amazing! I wonder how to customize "Recent" tabs to your welcome page. So I mean how to customize Recent tabs, Ask Watson AI Input etc. Can you help me or give me some advices?