Question

BIX Extract ruleset checkin issue

Initial EXTRACT rule and check-in works fine. However post that after checkout and making changes in filter conditions and then check-in, the filter criteria seems to be empty.

Steps to Reproduce

1. Use existing extract rule
2. Checkout and make changes to filter criteria, add additional filter or make changes to existing one
3. Save and checkin
4. refresh . The filter criteria will be cleared, all old or new filter criteria seems deleted

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Group Tags

Correct Answer
January 3, 2018 - 3:13pm

Upon reviewing the associated SR, I see that this was resolved by having you apply HFix-32803 and then Hfix-36122.

 

Comments

Keep up to date on this post and subscribe to comments

December 17, 2017 - 11:57am

Hello Jaya,

Could you please let us know the Pega version and Bix version used .

Enable logger on "com.pega.pegarules.data.internal.access.ExtractImpl"  and share us the log files .

Thanks,

Arun

 

 

Pega
December 17, 2017 - 12:11pm

Hello Jaya,

In my research, I can see few SRs with issue same yours for which the below two hotfixes are shared as the solution.

Hfix-32803

Hfix-36122

These hotfixes are for Pega 7.2.2. If you are on the same version then you can try these.

Note: Take DB backup before installing hotfixes as precautionary measure(to revert DB incase of any issues).

Thanks!

 

 

 

December 17, 2017 - 8:57pm
Response to gudam

Yes i am using 7.2.2.. Although we did not upgrade but nature of issue son check-in mentioned on these seems same. I will try and let you know

December 18, 2017 - 6:05pm
Response to JayaT745

Please let us know the SR number for reference once raised .

 

Pega
December 20, 2017 - 1:33am
Response to Arun_Mahanty

SR-C1712 seems to be the SR raised.

Thanks!

January 3, 2018 - 3:13pm

Upon reviewing the associated SR, I see that this was resolved by having you apply HFix-32803 and then Hfix-36122.

 

Marissa | Community Moderator | Pegasystems Inc.