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.

Support Article

Custom style names: Pega does not accept legal characters

SA-19331

Summary



The PDN help documentation

https://pdn.pega.com/sites/pdn.pega.com/files/help_v71/procomhelpmain.htm#rule-/rule-portalskin/component/customstyles.htm  states that - 

User can specify a custom style on the Advanced tab of the cell properties panel. User must enter the custom style name. 
To add a custom style:
  1. Click Add item.
  2. Type a Style Name that describes the purpose, rather than the style, using lowercase characters and hyphens, as needed. Note the primary category of purpose first, for example, ".marker-form-error", not FormErrorMarker_DivWhite". custom_ is prepended to the class name that you specify.
  3. Define the style in the CSS field. Click the magnifying glass to open the Style Editor. 
    To edit an existing custom style, click in the row that you want to edit, and then the magnifying glass to open the Style Editor.

However, PRPC does not allow such a style name.

When user attempts to save the skin, following error is observed: 

pyName: ** Invalid style for Custom Styles - style '.marker-form-error': only alphanumeric characters and spaces are allowed.


Error Messages



pyName: ** Invalid style for Custom Styles - style '.marker-form-error': only alphanumeric characters and spaces are allowed.


Steps to Reproduce



1) Open a Skin. For example OOTB pzDesignerStudio.

    

2) Add a custom style. Use the example custom style name from the online help: ".marker-form-error" . The name gets appended to custom_.marker-form-error as mentioned in the online help. 

    

3) Save the skin rule. Observe the error.

    

Root Cause



This issue occurs because the custom format is store as Embed-Skin-Component instead of Embed-Skin-Component-Custom. To resolve this problem, the Grid source formats of Embed-Skin-Component-Custom needs to be changed.

Resolution



Apply HFix-25775 to resolve this issue.

Published February 15, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us