Okay if WBSAVEAS is the only rule that it makes changes then I guess it is pretty safe, Actually everything in DEV environment was working fine, but after installing this hot fix , I have started facing the problem like Unable to View Decision Table, Unable to View Harness.
So was trying to check if this is the hotfix that was causing the problem.
You can cross check by doing private edit of the previous version of this activity WBSAVEAS and test your cases, i feel the issues would not be because of that. However better to quickly cross validate.
Also it issue still persists, it proofs that issues are not because of that hotfix and you can move that hotfix to other env and then cross test.
Regarding other issues you can cross check by loggin as OOB operator (firstname.lastname@example.org) and see if you face the issue with some OOB rules , if yes, please raise a SR. Else its because of some customization at your end.
I'm happy to see that HFix-24358 solved your problem.
I notice in your initial post that you cited DL-50825. zip, instead of the HFix# and your SR#.
Caution: DL files track a hotfix delivery to a specific customer. They are 1:1 deliverables that track which customers got a hotfix. As such, DL files should not be reused.
Curious about your concern about the reliability of the hotfix delivered in DL-50825, I looked up the DL in the internal tracking system, saw that it delivered HFix-24358, and ran the report that identifies how many times and to whom HFix-24358 was delivered. The latest report shows that HFix-24358 was delivered four (4) times to Pega-internal users. Besides DL-50825, there are three other DLs that delivered HFix-24358 between October 9 and November 19, 2015. Your DL is not listed in the report. That's very odd.
If you received DL-50825, DL-50801, DL-49667, or DL-49632 [used files!], process is not being followed and your hotfix delivery is not tracked in the system. Not good. Your DL package of HF-24358 should appear in the report as the first delivery of the hotfix to an external (business partner) customer (Accenture) and with a December 2015 date.
I hope that this info is useful to you and others, particularly those responsible for ensuring that we maintain reliable data in our tracking systems.
I searched for and found your SR in the PegaSupport application and traced the DL file that you originally cited at the top of this discussion as the file that was delivered to you by the GCS engineer resolving your case. Therefore, your hotfix shipment is tracked in the report. (I apologize for my misunderstanding.)
The traceability problem was caused by the facts that (a) I did not realize the original DL you cited was the one shipped to you from your SR and (b) the DL file was not generated from your SR.
Apparently the DL was explicitly created apart from your SR. This latter condition caused the DL file NOT to be listed in the References section of your SR.
As for any concern about citing DL numbers in this discussion, that is not a problem. Only a limited number of Pega employees has access to view DL information in the PegaSupport application. Clicking a DL file link here will prompt for authentication and fail for anyone without permission to view DLs in the PegaSupport application.