Helper class picker not working due to error in CSEndUser skin (included cs-icons stylesheet)
Hello,
I found this webpage that describes the exact problem we are facing: https://collaborate.pega.com/question/unable-view-list-helper-classes-pega-731
The file that is causing us the problem is a different file within a different platform version but the same issue remains, a broken helper class picker caused by a mistake in a stylesheet that is marked as final.
Pega platform 8.2.5
Pega Customer Service, v: 8
Pega Healthcare framework: v: 8
Skin CSEnduser within RS: PegaAppCA:08-02-02
Within that skin, the following style is included (as well as others - but the issue was isolated to this file):
- cs-icons (of RS: CPM:08-02-01)
- The bottom part of the file is incorrectly commented out.
The workaround, private edit, is to add the comment in the proper location and remove the */ at the end of the file. However, as it is a private edit on a final rule, it cannot be checked in.
Is there another way to fix this or is a GCS support ticket required?
The fix described below:
Original file:
/*
Note: Below icons are pointed to Platform font icons
.pcs-ssaicon1:before {
content: "\61";
}
….
Hello,
I found this webpage that describes the exact problem we are facing: https://collaborate.pega.com/question/unable-view-list-helper-classes-pega-731
The file that is causing us the problem is a different file within a different platform version but the same issue remains, a broken helper class picker caused by a mistake in a stylesheet that is marked as final.
Pega platform 8.2.5
Pega Customer Service, v: 8
Pega Healthcare framework: v: 8
Skin CSEnduser within RS: PegaAppCA:08-02-02
Within that skin, the following style is included (as well as others - but the issue was isolated to this file):
- cs-icons (of RS: CPM:08-02-01)
- The bottom part of the file is incorrectly commented out.
The workaround, private edit, is to add the comment in the proper location and remove the */ at the end of the file. However, as it is a private edit on a final rule, it cannot be checked in.
Is there another way to fix this or is a GCS support ticket required?
The fix described below:
Original file:
/*
Note: Below icons are pointed to Platform font icons
.pcs-ssaicon1:before {
content: "\61";
}
….
Fix:
(Description)By adding the */ after the note, and removing the */ at the bottom of the file, the helper class picker is properly showing all the helper classes available to the developer.
Resulting view of file:
/*
Note: Below icons are pointed to Platform font icons
*/
.pcs-ssaicon1:before {
content: "\61";
}
….
Pegasystems Inc.
US
Yes, if you want this change to persist on the final rule itself, you'll want to raise a support ticket. However, do please keep in mind our 8.x patch process/policies.
Serialized Solutions Inc
CA
Hi @Rett_Hean_GCS,
thank you for the reply. Yes, (if I recall properly), the patch process is typically on a monthly basis and all fixed hotfixes are accumulated as a part of that monthly patch. That covers for the platform. What I am not sure about is the patch process for the industry solutions. Is it the same process? I ask/confirm as I believe the fix for this is not within the Pega Platform but within the Customer Service product?
does that make sense?
thanks,
Rob
Pegasystems Inc.
US
Hi Rob, that is a fantastic question/point. You are correct. The 8.x patch process only applies to platform level fixes. If the fix needs to come from a strategic app rule, then this process may not apply.