Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Updating skins in Reporting

Suggest edit Updated on September 20, 2019

In Pega 7, you can format and style the Report Browser, Report Editor, and Report Viewer using PRPC skins. This lets you customize the appearance of these interfaces to suit your product needs.

You may want to customize the skin, and therefore the display, of these interfaces for two reasons.

  1. You want to change the formatting of reports to conform to your organization's style standards. For example, AcmeBank might have a corporate color palette which they strictly enforce for all their web applications.
  2. You may want to continue to use a pre-Pega 7 version of the Case Manager portal. Some formats used in the Pega 7 skins are not present in previous versions of the Case Manager portal, so if you want to use the older portal you may need to adjust some formats in order to improve the appearance of the Report Editor and Report Viewer.

If you have created custom skins for earlier versions of the Report Editor and Report Viewer, reports may not appear as you expect them to in Pega 7:

bad display of report

To resolve this issue, change your skin rule to point to Pega 7 rules, following the suggestions below.

If you are using the Case Manager 7 portal, this update is not necessary. Changing the skin in this situation could lead to styling conflicts.

 

Updating skins for the Report Editor and Report Viewer

If there is only a small discrepancy between the result you desire and they way reports display after you have upgraded to Pega 7, you could simply update your current custom skin. However, that involves copying a lot of formatting from the new Pega 7 skin into the custom skin. Therefore, Pegasystems strongly recommends that you begin by copying one of the existing Pega 7 skins, and then customize it to suit your needs.

Follow these steps:

  1. Locate and open the pyEndUser71 skin rule.
  2. Save a copy of the rule as pyReportingSkin. You must use this name as this is the skin referenced by the Report Viewer and Report Editor harnesses.
  3. Make any customizations you need to make on pyReportingSkin.
    Do not simply copy and paste from your existing custom CSS rule, as this will duplicate some code and could cause display problems.
  4. Expand the CSS tab and click Enable automatic generation.
    advanced tab of skin form
  5. Save your rule.

The skin rules need to be generated into CSS instances of the Rule-File-Text class. This happens at runtime by default. By clicking Enable automatic generation you cause the generation of the CSS instances immediately, in the RuleSet where you saved the copy of the skin. This lets the Report Viewer and Report Editor use the revised skin and style immediately.

Tags

Pega Platform 7.1.1 - 7.4 Reporting Financial Services Healthcare Insurance Media and Advertising Government Life Sciences Utilities Hospitality and Entertainment Manufacturing Retail
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us