Question
IBM
CN
Last activity: 5 Dec 2022 9:34 EST
PYSHOWSECUREFEATUREWARNINGS
Hi may I know why below issue happen?
After I click a button whose click action is to call a data transform, the data transform is not called, instead, as check in Tracer, a When rule PYSHOWSECUREFEATUREWARNINGS is called and return false, then nothing more is called.
Last night I did not meet this issue, but happen today. Thanks.
IBM
CN
More info, seems the issue happen after I check in the related section in a branch.
Before checking in, data transform is called normally, after checking in , it's not called, and even PYSHOWSECUREFEATUREWARNINGS not called.
IBM
CN
Seems the button click will not call any action after I check in the section. Nothing in Tracer too even I open monitoring for all rulesets
NCS Pte. Ltd
SG
Hi @MaxonL16591286: If I understand this correctly, the data transform is called when the section is in your private edit (checked out) and once you checked in into a branch it is not called.
If this is the case, please check if the same section is available in any other branch which are higher in precedence (you can use view siblings also). You can also add Stream Rules in tracer to check which section is getting used at run time.
You can also check the ruleset stack used from your profile.
Thanks.
IBM
CN
Hi, thanks.
Let's forget about PYSHOWSECUREFEATUREWARNINGS.
The problem is refined as:
I can call a CORRECT section in a case type, but the button click action will not work after the section is checked in. (Even Tracer return nothing after click).
After it's checked out, the button click action works but still only some clicks work and some other have same issue. So strange. I guess I need delete and re-create the section. Any other possible reason? thanks.
Pegasystems Inc.
IN
@MaxonL16591286 Hi Can you please check if you are using branch for development, if yes then please check if all your rules are in same branch. i.e. the data transform, the section, if you have created any properties all of them should be in same branch. If they are not in same branch please move them to same branch and check
IBM
CN
Hi , Thanks. Yes, all updated rules are in same branch, of course the rules which need not updated are not in any branch. Assume the branch I using is BRANCH1, the calling chain is as below: (NB means Not in any branch)
Case type (NB) -> first stage -> flow1 (BRANCH1) -> subprocess -> flow2 (NB) -> flow action 1 (NB) -> section 1 (NB) -> section 2 (BRANCH1),
in section 2, there's the button I mentioned above (button 1). It does not work after check in, and keep not work after check out. And, If i add a new button (button 2) after check out, the button 2 works some times.
IBM
CN
Move
section 2 (BRANCH1) -> button click -> call data transform (BRANCH1) -> set property1 (BRANCH1)
section 2 (BRANCH1) -> button click -> set value to field 1 (NB)
Pegasystems Inc.
IN
@MaxonL16591286 Hi, If that is the case can you please check the access group that you are using includes the branch that you are using
IBM
CN
Hi, thanks for prompt response. The Access group does include the branch, as confirmed.
And, for this weird issue I have solved it though root case not identified.
I guess it’s caused by I had copied the section from an existing complex section and then delete a lot things in it, and then add the button and text input.
Just now, I delete this section and copy again from another existing simple section (almost empty) and then just add fields without any deletion, the problem solved.
Anyway, many thanks!
IBM
CN
F.y.i, guess it’s caused by some invisible fields hide the button , so when I click the button, no any response, because Pega assign the click action to one of the invisible fields, not the button.
This may be identified by Live UI. However, the problem section has been deleted.
Thanks.