Skip to main content

Within the Knowledge Procedures, we have noticed that the font size is variable in 11.5, whereas now, it’s all uniform in other previous versions. Is there a way to format the font size and style to be consistent within a knowledge procedure in 11.5?  See attachment for example. 

 

Changes were made in 11.5 to improve the default styling of knowledge procedures. While the text is expected to look a bit different, it *should* be consistent. There are a couple of things that may be affecting what you are seeing.

 

1. One possibility is that the knowledge procedure itself has formatting applied to some of the text that may have previously had no visible impact to how it displayed in 11.4, but now with the 11.5 changes it stands out. For example if a block of text has had its font explicitly set in the editor. You would need to open the knowledge procedure in assyst and check in the editor if there's any extra formatting applied and potentially remove them.

 

2. If you are using a custom theme and specifically the same theme in 11.5 that you used for 11.4, css changes added to 11.5 may be conflicting with css in the older 11.4 change. You should be able to quickly confirm if this is the case or not by temporarily switching to the default out of the box theme called Amethyst. If the content looks better then you will need to rebuild your theme from 11.5. How you do this depends on how this theme was created originally - e.g. in-house or by an AGS representative. If the latter you should be able to contact them for assistance on building this otherwise it should be a case of following the same process you followed to create a theme for 11.4 except using the 11.5 css file as your starting point (More information is available on the wiki)

 

3. Styling overrides. Like with themes, styling overrides may be applied that affect the html being displayed. This is probably the least likeliest cause, but worth checking if none of the other reasons apply.

 

I'm not seeing this on my own 11.5 system so hopefully it's something above, but if none of the above things fix this then I'd suggest logging this with the support team in the normal manner so that someone can look into this further.


Reply