Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Hi Will,
Our team created this detailed document on feature comparison with QS to Reporting and Dashboarding - https://www.ibm.com/docs/en/SSEP7J_11.2.0/pdf/as_qs_compare.pdf


Also, you can use role customization to limit features of Authoring:


If you need anything further feel free to reach out directly to me denny.narezny@ca.ibm.com

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Hi Denny,

we have the same request but with Analysis Studio. I don't know how often I said to IBMers that the current approach of tweaking with the capabilities and their feature settings is not detailed enough.

• Let's talk about the toolbar: why the heck can't we limit the items that are visible in the toolbar per user roles? The only thing I can do is to enable or disable the whole thing instead of enabling single items.
• The same applies to the icon bar.
• Why depend the context menu on the data source? Framework Manager packages show more options than Data Modules.. why? No "Filter/Sort for report", no Lineage and no Glossary...
  
• Why can't we hide the padlock icon? I don't want users to accidentally activate the icon and play around with unlocked page objects.
• Why are the member-tree settings only available and stored in user cookies? I want to predefine those settings globally...
• Why is the search function in Report Studio limited? Users would like to state options (begins, contains, ends with ....)

Don't get me wrong. Report Studio is very powerful and we have functions do deactivate UI parts already - but not detailed enough.

Some of our key-users got a sneak preview of Report Studio and they were shocked of how overloaded with features the software was. They didn't want to use it and asked us if we could convince IBM to keep AS and QS alive... I know that won't happen but that's the real world. Not everyone want's to have a rocket-science studio to create pixel-perfect reports. They just want to analyse their data and quickly export it to Excel if needed.

Hi Will,
Our team created this detailed document on feature comparison with QS to Reporting and Dashboarding - https://www.ibm.com/docs/en/SSEP7J_11.2.0/pdf/as_qs_compare.pdf


Also, you can use role customization to limit features of Authoring:


If you need anything further feel free to reach out directly to me denny.narezny@ca.ibm.com

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Hi Denny,

remember Cognos 10? You could disable literarily EVERY single menu entry and button in the UI. Back then I build QS/AS lookalike interfaces for my customers based on RS that where really usable = without user training, like AS and QS.

Since RS has not changed since then except for the Glass GUI - it cannot be so hard to provide the same level of custiomization with Cognos 12, can it?

Cheers

Christian Seiser

Hi Denny,

we have the same request but with Analysis Studio. I don't know how often I said to IBMers that the current approach of tweaking with the capabilities and their feature settings is not detailed enough.

• Let's talk about the toolbar: why the heck can't we limit the items that are visible in the toolbar per user roles? The only thing I can do is to enable or disable the whole thing instead of enabling single items.
• The same applies to the icon bar.
• Why depend the context menu on the data source? Framework Manager packages show more options than Data Modules.. why? No "Filter/Sort for report", no Lineage and no Glossary...
  
• Why can't we hide the padlock icon? I don't want users to accidentally activate the icon and play around with unlocked page objects.
• Why are the member-tree settings only available and stored in user cookies? I want to predefine those settings globally...
• Why is the search function in Report Studio limited? Users would like to state options (begins, contains, ends with ....)

Don't get me wrong. Report Studio is very powerful and we have functions do deactivate UI parts already - but not detailed enough.

Some of our key-users got a sneak preview of Report Studio and they were shocked of how overloaded with features the software was. They didn't want to use it and asked us if we could convince IBM to keep AS and QS alive... I know that won't happen but that's the real world. Not everyone want's to have a rocket-science studio to create pixel-perfect reports. They just want to analyse their data and quickly export it to Excel if needed.

Hi Will,
Our team created this detailed document on feature comparison with QS to Reporting and Dashboarding - https://www.ibm.com/docs/en/SSEP7J_11.2.0/pdf/as_qs_compare.pdf


Also, you can use role customization to limit features of Authoring:


If you need anything further feel free to reach out directly to me denny.narezny@ca.ibm.com

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Christian, I totally agree! In Cognos 10 we had the ability to adjust the RS UI in detailed granularity - that was brilliant! 

One of the features that were already there, that are much missed today and IBM is not on the track to bring them back, unfortunately. And even if we don't get the ability back to adjust every single button in RS, it would be great to have a toggle switch which allows us to shrink RS UI down to a "Analyse" view that is much simpler to use for end-users.

Hi Denny,

remember Cognos 10? You could disable literarily EVERY single menu entry and button in the UI. Back then I build QS/AS lookalike interfaces for my customers based on RS that where really usable = without user training, like AS and QS.

Since RS has not changed since then except for the Glass GUI - it cannot be so hard to provide the same level of custiomization with Cognos 12, can it?

Cheers

Christian Seiser

Hi Denny,

we have the same request but with Analysis Studio. I don't know how often I said to IBMers that the current approach of tweaking with the capabilities and their feature settings is not detailed enough.

• Let's talk about the toolbar: why the heck can't we limit the items that are visible in the toolbar per user roles? The only thing I can do is to enable or disable the whole thing instead of enabling single items.
• The same applies to the icon bar.
• Why depend the context menu on the data source? Framework Manager packages show more options than Data Modules.. why? No "Filter/Sort for report", no Lineage and no Glossary...
  
• Why can't we hide the padlock icon? I don't want users to accidentally activate the icon and play around with unlocked page objects.
• Why are the member-tree settings only available and stored in user cookies? I want to predefine those settings globally...
• Why is the search function in Report Studio limited? Users would like to state options (begins, contains, ends with ....)

Don't get me wrong. Report Studio is very powerful and we have functions do deactivate UI parts already - but not detailed enough.

Some of our key-users got a sneak preview of Report Studio and they were shocked of how overloaded with features the software was. They didn't want to use it and asked us if we could convince IBM to keep AS and QS alive... I know that won't happen but that's the real world. Not everyone want's to have a rocket-science studio to create pixel-perfect reports. They just want to analyse their data and quickly export it to Excel if needed.

Hi Will,
Our team created this detailed document on feature comparison with QS to Reporting and Dashboarding - https://www.ibm.com/docs/en/SSEP7J_11.2.0/pdf/as_qs_compare.pdf


Also, you can use role customization to limit features of Authoring:


If you need anything further feel free to reach out directly to me denny.narezny@ca.ibm.com

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

I haven't found a way to stop users from editing reports. You can stop them from saving over a report, but you can't stop them opening the report and saving elsewhere. This is an overlooked area. Sometimes we don't want users to be able to see how a report works, or taking an existing report and modify it. Same with a datasource - sometimes there are datasources I don't want users to be able to create adhoc content against.

(Hopefully) someone will come along and show me I am wrong though :)

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Hi together,

I didn't find the time yet to test this out, but it should be possible to deny the edit button to users who can use Report Studio on read-only reports.

Open the properties of the folder and go to the Capabilities settings.

Click "Set capabilities" and a new windows will open. Now you can override the settings from the parent element and adjust the capabilities for this folder and its descendants. Simple deny Report Studio and it's done. The con against this solution is that it shifts your security model to way much higher and complex level as you have to keep in mind that you have security AND capabilities set on folder level. Please, let me know if this helps.

I haven't found a way to stop users from editing reports. You can stop them from saving over a report, but you can't stop them opening the report and saving elsewhere. This is an overlooked area. Sometimes we don't want users to be able to see how a report works, or taking an existing report and modify it. Same with a datasource - sometimes there are datasources I don't want users to be able to create adhoc content against.

(Hopefully) someone will come along and show me I am wrong though :)

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

This should work with Cognos 11.1, 11.2 and 12.0

Hi together,

I didn't find the time yet to test this out, but it should be possible to deny the edit button to users who can use Report Studio on read-only reports.

Open the properties of the folder and go to the Capabilities settings.

Click "Set capabilities" and a new windows will open. Now you can override the settings from the parent element and adjust the capabilities for this folder and its descendants. Simple deny Report Studio and it's done. The con against this solution is that it shifts your security model to way much higher and complex level as you have to keep in mind that you have security AND capabilities set on folder level. Please, let me know if this helps.

I haven't found a way to stop users from editing reports. You can stop them from saving over a report, but you can't stop them opening the report and saving elsewhere. This is an overlooked area. Sometimes we don't want users to be able to see how a report works, or taking an existing report and modify it. Same with a datasource - sometimes there are datasources I don't want users to be able to create adhoc content against.

(Hopefully) someone will come along and show me I am wrong though :)

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Great stuff. I will have a play with this. I never thought of capabilities on a folder!

This should work with Cognos 11.1, 11.2 and 12.0

Hi together,

I didn't find the time yet to test this out, but it should be possible to deny the edit button to users who can use Report Studio on read-only reports.

Open the properties of the folder and go to the Capabilities settings.

Click "Set capabilities" and a new windows will open. Now you can override the settings from the parent element and adjust the capabilities for this folder and its descendants. Simple deny Report Studio and it's done. The con against this solution is that it shifts your security model to way much higher and complex level as you have to keep in mind that you have security AND capabilities set on folder level. Please, let me know if this helps.

I haven't found a way to stop users from editing reports. You can stop them from saving over a report, but you can't stop them opening the report and saving elsewhere. This is an overlooked area. Sometimes we don't want users to be able to see how a report works, or taking an existing report and modify it. Same with a datasource - sometimes there are datasources I don't want users to be able to create adhoc content against.

(Hopefully) someone will come along and show me I am wrong though :)

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

This should work with Cognos 11.1, 11.2 and 12.0

Hi together,

I didn't find the time yet to test this out, but it should be possible to deny the edit button to users who can use Report Studio on read-only reports.

Open the properties of the folder and go to the Capabilities settings.

Click "Set capabilities" and a new windows will open. Now you can override the settings from the parent element and adjust the capabilities for this folder and its descendants. Simple deny Report Studio and it's done. The con against this solution is that it shifts your security model to way much higher and complex level as you have to keep in mind that you have security AND capabilities set on folder level. Please, let me know if this helps.

I haven't found a way to stop users from editing reports. You can stop them from saving over a report, but you can't stop them opening the report and saving elsewhere. This is an overlooked area. Sometimes we don't want users to be able to see how a report works, or taking an existing report and modify it. Same with a datasource - sometimes there are datasources I don't want users to be able to create adhoc content against.

(Hopefully) someone will come along and show me I am wrong though :)

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

In my excitement of thinking of capabilities on folders, I forgot the one obvious flaw that always bites. That if a user has read access they can just copy the report and put it somewhere that they can then edit the copy.

This should work with Cognos 11.1, 11.2 and 12.0

Hi together,

I didn't find the time yet to test this out, but it should be possible to deny the edit button to users who can use Report Studio on read-only reports.

Open the properties of the folder and go to the Capabilities settings.

Click "Set capabilities" and a new windows will open. Now you can override the settings from the parent element and adjust the capabilities for this folder and its descendants. Simple deny Report Studio and it's done. The con against this solution is that it shifts your security model to way much higher and complex level as you have to keep in mind that you have security AND capabilities set on folder level. Please, let me know if this helps.

I haven't found a way to stop users from editing reports. You can stop them from saving over a report, but you can't stop them opening the report and saving elsewhere. This is an overlooked area. Sometimes we don't want users to be able to see how a report works, or taking an existing report and modify it. Same with a datasource - sometimes there are datasources I don't want users to be able to create adhoc content against.

(Hopefully) someone will come along and show me I am wrong though :)

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.

Hi Marc,

yep, that's the last issue I couldn't resolve yet and I assume that there is no solution for it. We can't block users from copying objects locally. The only point that would help is to remove the whole option in the menu via feature modification in roles:

In my excitement of thinking of capabilities on folders, I forgot the one obvious flaw that always bites. That if a user has read access they can just copy the report and put it somewhere that they can then edit the copy.

This should work with Cognos 11.1, 11.2 and 12.0

Hi together,

I didn't find the time yet to test this out, but it should be possible to deny the edit button to users who can use Report Studio on read-only reports.

Open the properties of the folder and go to the Capabilities settings.

Click "Set capabilities" and a new windows will open. Now you can override the settings from the parent element and adjust the capabilities for this folder and its descendants. Simple deny Report Studio and it's done. The con against this solution is that it shifts your security model to way much higher and complex level as you have to keep in mind that you have security AND capabilities set on folder level. Please, let me know if this helps.

I haven't found a way to stop users from editing reports. You can stop them from saving over a report, but you can't stop them opening the report and saving elsewhere. This is an overlooked area. Sometimes we don't want users to be able to see how a report works, or taking an existing report and modify it. Same with a datasource - sometimes there are datasources I don't want users to be able to create adhoc content against.

(Hopefully) someone will come along and show me I am wrong though :)

@Marc 

Great idea! I will try and create a template that is similar. Question....if we grant Report Studio to users, will they be able to edit existing Canned Repots? We would not want them to see the existing canned reports in Report Studio.

One thing that really helped my users was adding my own 'Simple List' template to the report studio templates:

When this is used they get a report that looks like this:

to give them a default that looks as close to standard QS as possible.

It has a list, an easily changed title, filter text (so any added filters can be seen in the title area, just like QS) with page number footers.

@RACHEL SU With QS being deprecated, just adding this one simple template to the standard Report Studio set would help users a lot.

Since Query Studio is going away, is there a way to "dummy down" Report Studio to make it as simple to use for "non-techie" users? Most of our users are used to dragging and dropping and simple Ad-Hoc requests. I fear they will be overwhelmed and revolt against the use of Report Studio. How can I make it as simple as possible and not allow them to get stuck and bombard our help desk?

Thanks in advance.....we have been using Query Studio for over 15 years now.