Undo/Redo: Disable or Change Beaviour

[ThePencil]

Dear Ladies and Gentleman,

we have several applications on a TM1-Server.
With one of these applications we have problems with the undo/redo-function. Because of a complex combination of reports and processes, it is not transparent for the user what undo triggers.
Therefore we are looking for a solution to disable undo/redo in TM1-Web for this application.
Another possibility would be something like a commit function of the TM1-Undo/Redo-Stack, in which commit has the meaning the user should just have the possibility to undo actions until the last commit.

Additional we have two auxiliary conditions:
- a deactivation of cube logging is not possible
- this solution may affect only the target application and not all applications on the server

We would be very pleased, if anyone has an idea for this or would share his experience with us.

Kindly regards
Peter

[declanr]

You can disable the entire toolbar by going into the web.config file and adjusting the following lines:

Code: Select all

  
<!-- If set to true, all websheet toolbars will not be displayed -->
<add key="HideWebsheetToolBar" value="false;AllowOverwrite=true" />
<!-- If set to true, all Cubeviewer toolbars will not be displayed -->
<add key="HideCubeviewerToolBar" value="false;AllowOverwrite=true" />

Of course, this will also get rid of the recalc buttons and sandboxing etc but you can include workarounds for them if you need them (from the simple Shift+F9 / F9 to recalc all the way up the slightly more "complex" building of sandboxes through TI processes)

Also changing the web.config file will make it apply to all users whereas you can just change settings for individuals in the }clientsettings cube - in my opinion; both alteration of the config file parameters and the control cube parameters are EXTREMELY under utilised and the majority of Administrators could benefit from familiarising themselves with the options available to them during the early days of implementation... of course that's not to say it's the fault of the users, IBM could/should document such options better (along with documenting a lot of other stuff better) and it is also worrying how many "experienced" consultants are not even aware of some of the more fundamental parameters... I of course wouldn't expect a consultant to know ALL of the options but I would expect them to know the fundamentals or as a very minimum know where to look to see if they exist.

Rant over.

I hope this helps.

P.S. assuming that all of your services use the same web server - you will need to change the control cubes rather than the config file if you want to be able to control each service separately.

[ThePencil]

Hello Declan,

thank you for your answer.
Sorry for not mentioning it in my opening post: The solution with disabling the toolbar is the state we are running the application temporarily, so that we get no problems with undo.
But this is not accepted by our users. They want the toolbar, mostly beacuse of the export functions embedded in the toolbar.
Hence we are a looking for a way to get the undo function disabled without the sideeffect of losing the toolbar.
For this we just found up to now two possibilities: Disabling logging or modifying the webfiles (affecting all applications). These (no log or affecting other applications) are also sideeffects we do not want to have. Therefore we are looking for further possibilities.

Kindly regards
Peter