Question
Virtusa Corporation
US
Last activity: 29 Apr 2022 8:46 EDT
Unable to Save as Section using Design Template
I am unable to do save as of a section that contains Design Template. When I do "save as" and click "create and Open", getting an error as shown in the attachment. In the logs also, same error is captured. When I traced to see what caused the error, I found out that the obj-save in the pzRuleCheckOut is failing with the following errors. I understood that the obj-save step trying to save to same existing version but not sure why. Appreciate any help on resolving this issue. (Rule-UI-View)Database-Authorization-SaveToSecureRuleSetVersion RULE-UI-VIEW BB-DATA-CANDIDATE CAPTURECANDIDATEINFO #20220417T085832.672 GMT BB 01-01-01 You cannot save instance RULE-UI-VIEW BB-DATA-CANDIDATE CAPTURECANDIDATEINFO #20220417T085832.672 GMT to locked RuleSet BB:01-01-01
Accepted Solution
Updated: 29 Apr 2022 8:46 EDT
Pegasystems Inc.
IN
@GanapathyG Under Rule-UI-View class instances, you will find CaptureCandidateInfo rule. Can you do check out or private edit of this view rule and then save as your section.
Evoke Technologies
US
@GanapathyG I think this happens when some one already clicked on private edit of that rule, before u try to save as..!
Virtusa Corporation
US
@AkshithReddyTThanks for your reply. But that is not possible in my case as I am the only one using that application in my local machine.
Accepted Solution
Updated: 29 Apr 2022 8:46 EDT
Pegasystems Inc.
IN
@GanapathyG Under Rule-UI-View class instances, you will find CaptureCandidateInfo rule. Can you do check out or private edit of this view rule and then save as your section.
Virtusa Corporation
US
@pudua I am able to Save as, after keeping the corresponding view rule in private checkout. Thank you. But is this the expected behavior for saving as a section having view rule?
Pegasystems Inc.
IN
@GanapathyG Whenever a section rule is updated system will try to update its corresponding View rule, and if system is unable to acquire lock on this view rule, we usually see this issue and this is expected behavior.