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

Strategy Pallet UI Issues in Pega Marekting Portal

SA-30952

Summary



If a strategy is viewed via Designer Studio, and the Pega Marketing portal there are some styling issues in the Marketing portal due to differences between the skins used by each portal. User is interested in finding out if these are known issues (they are also reproducible in 7.21) with plans to fix, and for guidance on the best local changes.

Issue 1 - Labels are not shown on the Test Run Panel (Highlighted in yellow below).
Issue 2 - Pane expand or collapse icon is not rendered in the Pega Marketing Portal (Highlighted in green below).




Error Messages



Not applicable


Steps to Reproduce



Open a strategy rule in Designer Studio and the Pega Marketing Portal.

Root Cause



Issue 1: This is due to a difference between the designer studio and PegaMarketing portal skins.

The PegaMarketing skin is based on the pyEndUser skin from the UI Kit and does not exactly replicate everything from the Designer Studio skin.

As shown below one can see that the format “Simple List” which is used by the section where the labels are missing specifies that the labels should be positioned left in the designer studio, but in the PegtaMarketing skin are hidden (none).

Issue 2 is due to a missing font.

Resolution



Perform the following local-changes:

Issue 1: Missing text input Labels

It is not recommended to update the PegaMarketing skin label position for SimpleList as this will likely have an impact on various other parts of the portal where the label are intended to be hidden.

The solution here would be to override the standard pyExternalInputRunConfig section and change the format of the Dynamic Layout to something else that has the labels in both skins, for example, “Stacked” should work.





Issue 2: Link image for strategy pallet.

This issue is caused the font that has been specified has not been loaded.

A local change that corrects this would be to include the px-pega-default-icons style sheet as the second row in the PegaMarketing skin rule as shown below.



Both of these issues will be addressed in a future release of Pega Marketing.




Suggest Edit

Published August 23, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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