UserWork form calling a Decision Table makes issue with opening all other Decision Table because of the HOT-FIX-Bug-176811
Hi Team,
As part of one business functionality implementation i need to call a decision table from user Work form.
I use below syntax to call DT.
var pagename='<%=pega_rules_decisiontable.ObtainValue(tools,tools.findPage("pyWorkPage"),"GetGAPageName",false)%>'
Because of this am unable to open Decision Tables in designer Studio.
Attach are errors am getting when doing inspect element.
Somebody pls help to fix this.
Else pls suggest any other syntax to refer DT(Decision Table)
Regards
Aswana
***Moderator Edit-Vidyaranjan: Updated SR details***
-
Like (0)
-
Added more information:-
Actually there we are defining the pagename variable, which is in runtime getting assigned with values containing script tags and all other html fragments inside the variable for example: var pagename= ‘ <script> </script> …. HTML Fragments.’
a javascript variable value can’t be assigned in this way, Also the same is conflicting with decision table codes.
We need to return only the Page Name.
Regards
Aswana

Hello,
Why are you doing all this on "UserWorkForm"? Would it be just easier to use one of our place holder on an Activity?

Hi As part of SR-C47556,Pega given this solution.
can u suggest is there any other way to set variables when harness loads
Regards
Aswana

Pega did not give this solution. The SR described how to set a clipboard page property to a variable in an external JS file.
This post describes another set of custom JS to call a decision table form UserWorkForm which is now causing ruleforms to not load properly.
I think you should take a few steps back here to describe exactly what sort of business requirement you are trying to achieve which has led you down this approach? We may be able to offer some better alternatives here.

Oh I see, it was to set a variable in JavaScript on load of the harness.

Yes.
You aware about any other syntax to call decision table?
Regards
Aswana

We're awaiting the user's response to @Rett_Hean_GCS's reply