Limit Download as Speadsheet operation in RQM
SITUATION
I have a customer who is doing a lot of testing for a large project and on previous projects they developed a practice of exporting test execution results onto a page in a Excel spreadsheet which has a number of rollup reports, etc.
On this new project, they are running into some issues with large number of test execution results and the resources it consumes when requested and we are analyzing ways to keep this from impacting other usres.
QUESTION
1. Is there any way to limit the Download as Spreadsheet operation? In RQM 5.0.2, I do not see any permission setting that controls this.
2. Is there any way to remove the Download as Spreadsheet as an operation from a Project Area? I know this is a long shot, but just asking.
I have a customer who is doing a lot of testing for a large project and on previous projects they developed a practice of exporting test execution results onto a page in a Excel spreadsheet which has a number of rollup reports, etc.
On this new project, they are running into some issues with large number of test execution results and the resources it consumes when requested and we are analyzing ways to keep this from impacting other usres.
QUESTION
1. Is there any way to limit the Download as Spreadsheet operation? In RQM 5.0.2, I do not see any permission setting that controls this.
2. Is there any way to remove the Download as Spreadsheet as an operation from a Project Area? I know this is a long shot, but just asking.
Accepted answer
There is no option to disable the support of CSV Export i.e. Download as Spreadsheet. The CSV Export supports filters of the list view so the users should limit the amount of data using the filters before invoking the export. Please submit an enhancement request if there is a need to add restriction in the projects level or users level.
Comments
Don Yang
Oct 28 '15, 8:37 p.m.I don't think there is any existing options to either remove the menu or limit using that operation. But given that this menu is not there in old version such as v3.x, I guess the dev team should have a way to remove it.