Serious issue related to TM1Web Undo button

[ardi]

So we just discovered a huge issue with TM1Web undo button. We are using TM1 10.2.2, and yesterday I noticed that, if you by accident click the UNDO button, it will undo the last transactions entered manually by any user, and even worse, if the last transactions are a TI process load, then will try to undo those too. So if you have access to the cubes impacted from those transactions, the Undo, will undo them all. If not, then your "undo" will never end.
So it looks like when Undo in initiated from a TM1 Websheet, it does not look at the previous transaction or transactions only entered or loaded by that user/in that specific websheet, but everywhere. I contacted IBM and they say disable cube logging. We cannot disable cube logging since we need to be able to trace who entered what, so we are looking for an option to grayout Undo/Redo from TM1Web toolbar

Has anyone of you ever experienced this?

Thanks

[Oratia623]

Yes! We are also dealing with this beast.
Running TM1 10.2.2 and we sporadically will have the entire TM1 instance hang when a user presses UNDO on a websheet.
It is not every time UNDO is pressed, only sometimes.
No matter what we (admins) do, we have not been able to replicate the issue, even logged under user accounts.

I am really interested in your statements:
1) "it will undo the last transactions entered manually by any user,"
2) "So if you have access to the cubes impacted from those transactions, the Undo, will undo them all. If not, then your "undo" will never end. "

Certainly the never-ending-undo, is exactly what we have been experiencing, and we have the situation where the users who have been pressing undo, do not have access to all cubes.

How have you determined what the web undo button is actually attempting to do? (ie undoing all transactions to all cubes and the never end caused by no access to the cube)

IBM did not seem aware of this and also just suggested we turn off logging, which we also cannot do (additionally, this does not sound like it would work unless you turned of logging to ALL cubes)
IBM have asked us to run a server logging dump during the hanging period to try and diagnose what the cause is, an invasive and lengthy process when we really need to get the system back up.

We don't really want to disable the undo button, as it seems to work most(?) of the time.

You are not alone.

[moby91]

Is this related to the APAR PI27900 ?

http://www-01.ibm.com/support/docview.w ... wg1PI27900
PI27900: TM1WEB UNDO BUTTON BECOMES ACTIVE. SAVES DATA WHEN CLICKED.

[moby91]

We are using TM1 10.2.2, and yesterday I noticed that, if you by accident click the UNDO button, it will undo the last transactions entered manually by any user, and even worse, if the last transactions are a TI process load, then will try to undo those too. So if you have access to the cubes impacted from those transactions, the Undo, will undo them all. If not, then your "undo" will never end.

What happens when you isolate the transactions done by the TI process from the transactions entered manually by any user, for instance by adding a TI fct SaveDataAll or less intrusive a TI fct CubeSaveData as last commands into the epilog of your TI process ?

[ardi]

SaveData does not help. EVen after the savedate is executed ( through TI or manually ), still the UNDO will go to the previously saved tm1sXXXXXXX.log files.

It is so easy to reproduce. So if you have a websheet with an Action button that runs a TI process and click on it, then after the TI is finished executing, if you try the UNDO button, it will undo the data. So far nothing wrong if we assume that in the new version, the UNDO button can undo even data committed/loaded from action buttons.
If you click on the action button again and ask some other user who also has access to run that button and also has access to all cubes, then he will undo the data also, so this is where you start suspecting that UNDO is doing something is not supposed to
If you click again on that action button and ask a user who has no access to run the action button and also has limited access to the cubes loaded from that TI, then in TM1Top you see an activity related to that user session trying to Undo but this never ends.

But this gets worse.
Go as admin user and try to edit a cell ( I have a control cube that only admin user has WRITE access to ), and ask a user to connect, by the way the undo button should be grayed out when users connect and they are only in the landing page, but it is not grayed out, and if the user clicks on it ( after the admin user has modified a cell in CONTROL cube ), then the undo never ever finishes.

Also if you have USER A ( non-admin ) who has access to Location_A and modifies his data, and if USER_B (non-admin) who has access to only Location_B, then if he tries the undo (after USER_A has made a change ), the undo never finishes

So we talked to IBM and on Friday afternoon we had a conference call with many people from IBM, including Development Managers, we were able to make them see the issue, and they admitted this is a bug. There is no fix available, but they are trying to give us a solution to hide the Undo/Redo buttons from Websheet Toolbar

[Oratia623]

Awesome ardi!

We had not seen/suspected this behaviour, and could not for the life of us reproduce the hang.
Really looking forward to reproducing the issue using your instructions and adding our voice to IBM to get this fixed properly.

Thanks

[ardi]

Awesome ardi!

We had not seen/suspected this behaviour, and could not for the life of us reproduce the hang.
Really looking forward to reproducing the issue using your instructions and adding our voice to IBM to get this fixed properly.

Thanks

Were you able to reproduce the issue?

[blackhawk]

We have also seen this issue at a customer. We ended up removing the undo and redo button from the UI.

If anyone is interested in how to do this until IBM fixes the issue, just follow the steps below:

• Go to the directory C:\Program Files\ibm\cognos\tm1_64\webapps\tm1web\scripts\tm1web\standalone
• Make a backup of the original TM1WebApp.js file
• Open up TM1WebApp.js
• Search for _79
• Delete the text _79.add(this.items.undoButton); _79.add(this.items.redoButton);
• Save the file

You may need to clear the cache on your browser to load the change in, but that will remove the two undo and redo buttons for now.

It won't fix the problem, but at least it will prevent users from clicking on the button and causing havoc.

[Buffa]

Curious if you have any interim fix packs (IF's), or official fix packs (FP's) installed? We are on 10.2.2 IF3 which is pre-FP1, and I can't reproduce the issue. We do have cube logging enabled, but I can only undo my committed entries. Another user can't undo mine. Maybe they fixed this in FP1? Or maybe it has to do with some other setting. What security mode do you use? We use Mode 5, integrated with Cognos BI. I wonder if that changes how the undo queue is set per user? Just throwing some ideas out there.

[ardi]

Curious if you have any interim fix packs (IF's), or official fix packs (FP's) installed? We are on 10.2.2 IF3 which is pre-FP1, and I can't reproduce the issue. We do have cube logging enabled, but I can only undo my committed entries. Another user can't undo mine. Maybe they fixed this in FP1? Or maybe it has to do with some other setting. What security mode do you use? We use Mode 5, integrated with Cognos BI. I wonder if that changes how the undo queue is set per user? Just throwing some ideas out there.

Did you just try to enter a number, recalc the websheet and ask another user to connect right after and ask him to click on the Undo? IBM was able to reproduce and they confirmed there is no fix available. This happens in websheets only, not in TM1Web cubeviews

I can reproduce in any model

[Buffa]

Yes, those are the steps we followed, and we are using tm1 websheets. Interesting. Maybe there is some server setting we are using that somehow works around it. Also, only myself and another admin tested it. I guess we could have two non-admin users try it but I wouldn't think that would matter. Here are our tm1s.cfg settings we use, outside the Integrated Security 5 mode I mentioned earlier. Most surely aren't related, but providing them in case some weird combination stops it.


#### CPU Related Parameters
MaximumCubeLoadThreads=4
MTQ=8
ParallelInteraction=T

#### Performance Modeler/TM1 Applications Parameters
AllowSeparateNandCRules=T
#ForceReevaluationOfFeedersForFedCellsOnDataChange=T

#### General Parameters
Language=ENG
MaximumViewSize=6000
ExcelWebPublishEnabled=T
DisableSandboxing=F
MaximumMemoryForSubsetUndo=2000000
StartupChores=Admin - Populate Controls - At Startup
PersistentFeeders=T

We also made the following changes to C:\Program Files\ibm\cognos\tm1_64\webapps\tm1web\WEB-INF\configuration\tm1webconfig.xml. I'm not sure this could be related, but you never know for sure with these weird bugs.

"RecalcOnPicklistChange" value="true"
"RecalcOnActivate" value="false"

[ardi]

The only significant differences we have are below:

ServerLogging=F
SecurityPackageName=Kerberos
IntegratedSecurityMode=3
UseSSL=F
PersistentFeeders=F
DisableSandboxing=T

So probably Sandboxing or Security mode we are using are the cause of this issue

[moby91]

SaveData does not help. EVen after the savedate is executed ( through TI or manually ), still the UNDO will go to the previously saved tm1sXXXXXXX.log files.

It is so easy to reproduce. So if you have a websheet with an Action button that runs a TI process and click on it, then after the TI is finished executing, if you try the UNDO button, it will undo the data. So far nothing wrong if we assume that in the new version, the UNDO button can undo even data committed/loaded from action buttons.
If you click on the action button again and ask some other user who also has access to run that button and also has access to all cubes, then he will undo the data also, so this is where you start suspecting that UNDO is doing something is not supposed to
If you click again on that action button and ask a user who has no access to run the action button and also has limited access to the cubes loaded from that TI, then in TM1Top you see an activity related to that user session trying to Undo but this never ends.

But this gets worse.
Go as admin user and try to edit a cell ( I have a control cube that only admin user has WRITE access to ), and ask a user to connect, by the way the undo button should be grayed out when users connect and they are only in the landing page, but it is not grayed out, and if the user clicks on it ( after the admin user has modified a cell in CONTROL cube ), then the undo never ever finishes.

Also if you have USER A ( non-admin ) who has access to Location_A and modifies his data, and if USER_B (non-admin) who has access to only Location_B, then if he tries the undo (after USER_A has made a change ), the undo never finishes

So we talked to IBM and on Friday afternoon we had a conference call with many people from IBM, including Development Managers, we were able to make them see the issue, and they admitted this is a bug. There is no fix available, but they are trying to give us a solution to hide the Undo/Redo buttons from Websheet Toolbar

There is a new Interim Fix 5 for TM1 10.2.2 FP3, eAssembly Version Number 10.2.5230.1045, which includes a patch for the APAR PI39665:
TM1 Web allows users to undo another user's action

This seems to be your issue.

May I ask if your issue with the Undo button in TM1 Web 10.2.2 has been resolved by the Interim Fix 5 for TM1 10.2.2 FP3 ?