Workflow for making Skin Updates
When updating the Component Styles or Mixins for a skin in the Dev envioronment, we are only able to see changes after logging out, clearing browser cache, and then logging back in.
Are there cache settings in the Dev Studio to prevent this caching so that we can simply refresh the browser?
Also, what we are seeing in the Dev Studio when we change a component style or mixin, doesn't reflect on the front end. How can we over ride what ever inherited styles are overriding our skin settings?
Is there existing documentation providing guidance on this?
Thanks.
Pegasystems Inc.
GB
@DavidS597 please can you confirm the version of Pega you have installed?
Not sure whether you are directly logging to the application which launches end user portals or navigating from designer studio. Please check the following.
1) There is no different skin is defined in Operator preferences ( if you are launching end user portals from designer studio)
2) make sure that your portal level skin is configured with the correct skin rule
If you are using CSS changes to override the Pega stylings did you add these stylings in a separate css file and then attach it to the application skin? Then the styling can be applied to the entire application. It is best not to apply these changes in the UserWorkForm as it will be deprecated in releases 8.7 and above.
Are you not seeing changes even on the same node?
Did you check the steps outlined in this PCC question ?
Some of the skin formats created under skin rule are also managed through extra CSS styles in PEGA. So, if you need to changes the existing format for any control type in skin rule, update the skin rule as well check if there is any CSS which you might need to override in your application css worksheet.
@DavidS597 please can you confirm the version of Pega you have installed?
Not sure whether you are directly logging to the application which launches end user portals or navigating from designer studio. Please check the following.
1) There is no different skin is defined in Operator preferences ( if you are launching end user portals from designer studio)
2) make sure that your portal level skin is configured with the correct skin rule
If you are using CSS changes to override the Pega stylings did you add these stylings in a separate css file and then attach it to the application skin? Then the styling can be applied to the entire application. It is best not to apply these changes in the UserWorkForm as it will be deprecated in releases 8.7 and above.
Are you not seeing changes even on the same node?
Did you check the steps outlined in this PCC question ?
Some of the skin formats created under skin rule are also managed through extra CSS styles in PEGA. So, if you need to changes the existing format for any control type in skin rule, update the skin rule as well check if there is any CSS which you might need to override in your application css worksheet.
Can you confirm you change the mixin as per the documentation and here?
Digital FastForward
US
@MarijeSchillern Thanks for the detailed reply.
Yes, the skin we are modifying IS set in the configuration > definitions. We can see some of the changes we make to component styles after logging out, clearing cache and logging back in. We are not adding additional css in a style sheet - at the moment, simply trying to make changes to Component Styles and Mixins.
So the first question, is should there be cache-ing preventing us from simply refreshing the page and seeing changes (after checking in any edits we've made to the skin)? It seems quite tedious to have to log out, clear browser cache, and log back in each time.
When you ask "are you not seeing the same changes in the node" do you mean when editing the skin if we see the changes reflected in the sample content to the right? I'm not sure if you mean something else, but we are seeing the changes in the Preview content while editing the Component Styles and Mixins. However some are being overridden by external css. Some components do not have certain style attributes available to modify. ie Table Headings have a :focus attribute we can customize but not a :hover attribute, and there are inherited styles we want to modify. Do we need to use an external style sheet?
We tried to override those with an external style sheet but cannot. Our rules are ignored ( i can see in the inspector - they are crossed out b/c the inherited rule has higher precedence).
@MarijeSchillern Thanks for the detailed reply.
Yes, the skin we are modifying IS set in the configuration > definitions. We can see some of the changes we make to component styles after logging out, clearing cache and logging back in. We are not adding additional css in a style sheet - at the moment, simply trying to make changes to Component Styles and Mixins.
So the first question, is should there be cache-ing preventing us from simply refreshing the page and seeing changes (after checking in any edits we've made to the skin)? It seems quite tedious to have to log out, clear browser cache, and log back in each time.
When you ask "are you not seeing the same changes in the node" do you mean when editing the skin if we see the changes reflected in the sample content to the right? I'm not sure if you mean something else, but we are seeing the changes in the Preview content while editing the Component Styles and Mixins. However some are being overridden by external css. Some components do not have certain style attributes available to modify. ie Table Headings have a :focus attribute we can customize but not a :hover attribute, and there are inherited styles we want to modify. Do we need to use an external style sheet?
We tried to override those with an external style sheet but cannot. Our rules are ignored ( i can see in the inspector - they are crossed out b/c the inherited rule has higher precedence).
Is there a way to add those attributes to a mixin or component style, so we can set the :hover style from there?
Thanks!