Question

3
Replies
293
Views
 Henry Allen (HenryA80)
Veteran Careers First

Veteran Careers First
US
HenryA80 Member since 2015 59 posts
Veteran Careers First
Posted: April 2, 2021
Last activity: 4 weeks ago
Posted: 2 Apr 2021 22:09 EDT
Last activity: 7 Jul 2021 11:52 EDT
Solved

HTML /HTML Fragment/JSP rules do not appear in the menu for 8.5

Report

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

***Edited by Moderator Marissa to update Support Case Details***
Pega Customer Service 8.5 User Experience System Administration Upgrades Government System Architect Support Case Created Upgrade
Reply
Posted: 3 months ago
Posted: 26 Apr 2021 1:36 EDT
Gowrishankar Ramasamy (GOWRISHANKAR)
PEGA
Sr. Service Assurance Advisor Specialist
Pegasystems Inc.
IN
Report

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,

Reply

Accepted Solution

Posted: 1 month ago
Updated: 1 month ago
Posted: 28 Jun 2021 11:27 EDT
Updated: 28 Jun 2021 11:30 EDT
Henry Allen (HenryA80)
Veteran Careers First

Veteran Careers First
US
Report

@TashikaS   @GOWRISHANKAR 

Type of Incident: Product Resolution type: SolutionRoot cause: 3rd Party IssueRoot 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.

Show More

@TashikaS   @GOWRISHANKAR 

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" />

Show Less
Reply