Hi Venkat,

Hope you are talking about Pega7 application, in Pega 7 inline styles are not recommended, Pega 7 skin rule provides mixins and Formats which can be leveraged to apply rich styles to your UI components.

If you still continue to use in line styles then maintenance of your application will become very difficult.

Thanks,
Dhev

Yes. We are using the skin. In the Inline styles in pega 7, in Presentation - under Advanced presentation options, we are giving the "Cell read-write classes", "Cell read-only classes" with the class name. But even its not picking up the fromatting from that tag.

Eg) we are giving the Class name in the "dataLabelLeftStyle". But the formatting mentioned in the "dataLabelLeftStyle" is not getting applied to the cell. Instead the properties of "TD" is getting applied in all the places.

We are using skin which points to the

Hi Venkat,

Where and how did you create the style class specified for the read-only classes attribute?

Is tihs defined in a CSS Text File rule, if that is the case then where is this CSS Text File rule mapped - is it in the Harness rule or in the Skin rule?

Are you modifying or opening the workform_classic.css mapped Skin through the Pega 7 Skin rule form, or are you directly opening the workform_classic.css rule and making the required changes?

Thanks for the response.

We have mapped the CSS file in the Skin. We have not created any new CSS styles. It is a pega CSS file, so we are not modifying the contents of it. We are using the style which is already present in here for our application.

Instead of the "dataLabelStyleTop" styles, we are always getting the format of specified in "TD" style.

Text File:Work form styles for ProCom[Final]

ID  webwb • workform_classic • css

RS Pega-WB:07-10-01

.dataLabelStyleTop {

    font-weight: normal;

    color: #003366;

    font-family: Verdana, Arial, sans-serif;

    font-size: 8pt;

    text-align: right;

    vertical-align: top;

    padding: 0px 5px 0px 5px;

}

TD {

    font-family: Verdana, Arial, sans-serif;

    font-size: 8pt;

    font-weight: normal;

}

We tried a similar configuration, but we are not encountering the issue mentioned.

When it comes to CSS, better we create a custom CSS rule rather than mapping the existing CSS.

In your scenario the workform CSS, this might already be getting applied by Pega. So, referencing the same again through the additional CSS might not be a correct approach.

Also, as you are saying TD i feel that you are using Smart or FreeForm layouts, is that correct?

Yes we are and were using freeform layouts. We did not had any issue with it in Pega 6.1

We did not go for Custom CSS with our skin, so that during upgrade it will be automatically taken care. But it was other way around.

Since this is a Pega CSS, we have raised a SR with them now. Hopefully it should be fixed. Thanks for your help.