Question


Accenture
IN
Last activity: 6 Jan 2016 0:53 EST
Save As History is not captured in the Rule
When we perform a "Save As" on a rule.
Ideally history of the rule should be updated but in Pega 7.1.7 the history is not getting captured.
So there is a hot fix for this "HFIX-24358" which solves this.
Anyone here used this?
Any cascading problem faced on this? Like Rules not getting picked harness not getting displayed?
Message was edited by: Vidyaranjan Av
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Updated: 30 Dec 2015 7:02 EST


Accenture
IN
HFIX-24358 is provided by pega team, No issue faced after the fix.


JPMC
IN
This hotfix does not have any dependent hotfixes and the rule changes for this is only one rule as follows:
RULE-OBJ-ACTIVITY RULE- WBSAVEAS
Thus I feel its safe to use. Further as of now we have not heard back any side effect of this from any of the customers. Incase you see/ find anything please do let us know.


Accenture
IN
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.


JPMC
IN
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 ([email protected]) 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.
Updated: 7 Dec 2015 4:47 EST


Accenture
IN
Raised a SR with the pega team.
Thanks Ashish for your suggestion âº


JPMC
IN
Please share the SR number for tracking in this Post.
Accepted Solution
Updated: 30 Dec 2015 7:02 EST


Accenture
IN
HFIX-24358 is provided by pega team, No issue faced after the fix.


Pegasystems Inc.
US
Rasaiya,
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.
Rasaiya,
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.
-Mary
Updated: 31 Dec 2015 0:36 EST


Accenture
IN
Inboxed you details about the DL file. Removing DL info from the post.
Does only the DL number changes? or the content inside the DL also changes for the customer?
I mean hotfix is specific to customer? or just for tracking purpose it is given in DL number but the file is the same?


Pegasystems Inc.
US
Hi Rasaiya,
Yes, the DL number changes with every delivery of a hotfix to a customer (internal or external).
The DL content is the same for a given hotfix.
For example, the four hotfix delivery files (DLs) mentioned in this discussion all contain the same information; they all deliver HFix-24358.
(And this particular hotfix has no Additional Related Hotfixes, dependent hotfixes.)
Yes, as I mentioned above, the DL files track the number of times a hotfix was shipped, who got a particular hotfix, and when the delivery occurred.
I neglected to mention that for your hotfix delivery to be tracked, you should have submitted an SR for Product Defect.
Then you would have received your own DL file and that hotfix delivery would be tracked for your account in the Pega-internal report Track Particular Hotfix Shipped to Customers.
As it stands now, we still have no record of HFix-24358 being delivered to you.
-Mary


Accenture
IN
It seems not proper documentation done from person who handled the SR.?
Can you inbox me the person to whom my DL is delivered to?


Pegasystems Inc.
US
Hi Rasaiya,
Mystery solved.
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.
-Mary


Accenture
IN
okay âºâº