HTML /HTML Fragment/JSP rules do not appear in the menu for 8.5
HTML /HTML Fragment/JSP rules do not appear in the menu for 8.5 which is different than 8.3.
Is it possible HTML Fragment rules have been deprecated....
See Attachment
Accepted Solution
Updated: 28 Jun 2021 11:30 EDT
Veteran Careers First
US
Type of Incident: Product Resolution type: Solution Root cause: 3rd Party Issue Root cause description:
A third-party product issue - A bug in JBoss version, the server is only sending one PegaRULES cookie in the first response but the path is for /prweb/PRPushServlet/app/<appname>.There is a missing PegaRULES cookie that should have a path /prweb/app/<appname>.
https://issues.redhat.com/browse/UNDERTOW-1489
The default behavior with application url enabled is to identify application alias, we added the application alias in the path as an identifier. So when the user logs in, we are getting 2 pegarules cookies 1) for the application alias and 2) for PRPushServlet which is used for push notification.
Pega Platform 8.4+ is the first version where we started to add multiple cookies with same name and value but with different paths.
An application URL alias provides a URL that allows the use of multiple applications simultaneously in the same browser or embed multiple mashups in the same webpage.
Type of Incident: Product Resolution type: Solution Root cause: 3rd Party Issue Root cause description:
A third-party product issue - A bug in JBoss version, the server is only sending one PegaRULES cookie in the first response but the path is for /prweb/PRPushServlet/app/<appname>.There is a missing PegaRULES cookie that should have a path /prweb/app/<appname>.
https://issues.redhat.com/browse/UNDERTOW-1489
The default behavior with application url enabled is to identify application alias, we added the application alias in the path as an identifier. So when the user logs in, we are getting 2 pegarules cookies 1) for the application alias and 2) for PRPushServlet which is used for push notification.
Pega Platform 8.4+ is the first version where we started to add multiple cookies with same name and value but with different paths.
An application URL alias provides a URL that allows the use of multiple applications simultaneously in the same browser or embed multiple mashups in the same webpage.
Solution type: Local Change - Pega Rule Solution description: As a workaround, disable applicationalias by applying below DSS and restart the system - <env name="http/url/applicationalias/enabled" value="false" /> <env name="http/url/applicationalias/default/enabled" value="false" />
Citicorp Services India Private Limited
IN
Hi @HenryA80,
Yes HTML Fragment rules are deprecated. If you have those rules created in the application prior to Upgrade those should be working fine. If the rules created prior to upgrade don't exist please report this issue to pega support.
Thanks,
Pegasystems Inc.
IN
Can you refer - https://community.pega.com/knowledgebase/articles/user-experience/85/about-html-fragment-rules
https://community.pega.com/knowledgebase/articles/user-experience/85/html-rules
Accepted Solution
Updated: 28 Jun 2021 11:30 EDT
Veteran Careers First
US
Type of Incident: Product Resolution type: Solution Root cause: 3rd Party Issue Root cause description:
A third-party product issue - A bug in JBoss version, the server is only sending one PegaRULES cookie in the first response but the path is for /prweb/PRPushServlet/app/<appname>.There is a missing PegaRULES cookie that should have a path /prweb/app/<appname>.
https://issues.redhat.com/browse/UNDERTOW-1489
The default behavior with application url enabled is to identify application alias, we added the application alias in the path as an identifier. So when the user logs in, we are getting 2 pegarules cookies 1) for the application alias and 2) for PRPushServlet which is used for push notification.
Pega Platform 8.4+ is the first version where we started to add multiple cookies with same name and value but with different paths.
An application URL alias provides a URL that allows the use of multiple applications simultaneously in the same browser or embed multiple mashups in the same webpage.
Type of Incident: Product Resolution type: Solution Root cause: 3rd Party Issue Root cause description:
A third-party product issue - A bug in JBoss version, the server is only sending one PegaRULES cookie in the first response but the path is for /prweb/PRPushServlet/app/<appname>.There is a missing PegaRULES cookie that should have a path /prweb/app/<appname>.
https://issues.redhat.com/browse/UNDERTOW-1489
The default behavior with application url enabled is to identify application alias, we added the application alias in the path as an identifier. So when the user logs in, we are getting 2 pegarules cookies 1) for the application alias and 2) for PRPushServlet which is used for push notification.
Pega Platform 8.4+ is the first version where we started to add multiple cookies with same name and value but with different paths.
An application URL alias provides a URL that allows the use of multiple applications simultaneously in the same browser or embed multiple mashups in the same webpage.
Solution type: Local Change - Pega Rule Solution description: As a workaround, disable applicationalias by applying below DSS and restart the system - <env name="http/url/applicationalias/enabled" value="false" /> <env name="http/url/applicationalias/default/enabled" value="false" />
