ITMS Administrator Group

ITMS 7.5

Is it possible to disable the parameter caching on a single report? Simple enough question. Im looking for a way, through customizing the XML or through the report creator, to disable caching of report parameters. For instance, if you have Parameter A, and it is a string value, typing anything into the field will cause what is typed to be cached for later use of the report. So, if you leave the report, and come back at a later time, the report will have the last thing you typed in that field. How do we reset this programatically and not for all reports?

I have tried adding alwaysUseDefault="True" to the XML Style section for each parameter, but this does not seem to clear out the previous parameter. I will say, I use this for the date/time function when I want to specify the defaultValue as "today". Works great for date/time, but does not seem to work for string.

Any suggestions?

This should be configurable. Caching parameters may not be the wanted behavior on certain reports. The ability to toggle this per report would be greatly appreciated as it defeats the purpose of the default value. I understand it is the default for each new user for the 1st time they access the report. But, in cases where there are many parameter fields, you may not want the cached value each time you go to the report. Starting from the "clean" slate would be preferred.

Hi!

Yes, I see that parameter isn't changed back to default, which is set in root of report.

It works like personalization, because if report has default parameter value = "1" and:

1. If you're logged under "Account1" in SMP Console and changed report parameter from "1" to "2", then after returning back to this same report it will store same parameter"2".

2. If you will logon under "Account2" in SMP Console and open same report, then you will see that parameter will be default "1" and not "2", since "Account2" never changed it yet. Once "Account2" will change default parameter "1" to another one, then this changed parameter will be stored for this report and for this Account2 only.

• How to disable personalization:

You can go to C:\Program Files\Altiris\Notification Server\Bin\Tools and open NSConfigurator.exe tool ⇒ By default "PersonalizationEnabled" is enabled in CoreSettings.config but you can disable it and then you will don't have this problem with cached parameter in reports.

Thanks,

IP.

Yep, that will do it. Thank you Igor, this works great.

I have not tested it more than just the reporting aspect (it does not cache the previously used parameter strings when switching reports), but I am concerned about what other aspects of the console it affects. Hopefully I can post some results after I let my users work with it for a bit. I wont tell them I did this otherwise they will be coming up to me and complaining about petty things, even though this can be considered petty!!

Sorry that I didn't provide some affect areas results:

Quick look on this, if you will have a disabled personalization:

1) We talked above, reports parameters will be always default for all users in SMP Console.

2) Previouslly, if you was on some favourite SMP Console page and then closed it -⇒ On next opening SMP Console, you will always be on "First Time Setup" page, although when personalization was enabled, you were automatically moved to last place of SMP Console, instead of "First Time Setup" page.

From Altiris Log Viewer:

• Personalization is disabled. Settings for Altiris.NS.UI.Controls.NavigationHistory will not be loaded.
• Personalization is disabled. Settings will not be saved
• Personalization is disabled. Settings will not be saved

3) If you've added some custom web parts on "My Portal" page and will close I.E -⇒ then on next logon to SMP Console, "My Portal" page will be empty and will doesn't contain previouslly added web parts by you.

4) After each time of opening a report in SMP Console -⇒ it will throws a lot of unnecessary informational messages, which are mentioning about your disabled personalization.

I think that you will re-decide whether leave personalization disabled, or return it back to be enabled.

Thanks,

IP.

Haha...same thing I recognized when testing. As I am cleaning up the customer's console and having them use some of the webparts instead of exposing more of the console for them to do simple actions, I decided that removing their webparts on each reload was not ideal. Still would be a great idea to have these seperated so you can turn off report caching without having the rest of the console suffer.

Thanks again though.